From 28c2089c8d229b600bce5a66510fe1da3d61b80d Mon Sep 17 00:00:00 2001 From: hongkunyoo Date: Fri, 30 Nov 2018 13:53:20 +0900 Subject: [PATCH] Update on pod-priority-preemption.md (#11418) * number Pods --> number of Pods * add comma(,) for clarity. --- .../en/docs/concepts/configuration/pod-priority-preemption.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/configuration/pod-priority-preemption.md b/content/en/docs/concepts/configuration/pod-priority-preemption.md index 7ee796191da..909b5c01ab1 100644 --- a/content/en/docs/concepts/configuration/pod-priority-preemption.md +++ b/content/en/docs/concepts/configuration/pod-priority-preemption.md @@ -241,7 +241,7 @@ priority Pods to zero or a small number. #### PodDisruptionBudget is supported, but not guaranteed! A [Pod Disruption Budget (PDB)](/docs/concepts/workloads/pods/disruptions/) -allows application owners to limit the number Pods of a replicated application +allows application owners to limit the number of Pods of a replicated application that are down simultaneously from voluntary disruptions. Kubernetes 1.9 supports PDB when preempting Pods, but respecting PDB is best effort. The Scheduler tries to find victims whose PDB are not violated by preemption, but if no such victims @@ -329,7 +329,7 @@ than the victims. If preemption happens in such scenarios, please file an issue. When pods are preempted, they receive their requested graceful termination period, which is by default 30 seconds, but it can be any different value as -specified in the PodSpec. If the victim Pods do not terminate within this period +specified in the PodSpec. If the victim Pods do not terminate within this period, they are force-terminated. Once all the victims go away, the preemptor Pod can be scheduled.