From 0407c5500f28ed4f43f2821b49e4a89479184968 Mon Sep 17 00:00:00 2001 From: Ketankumar Jani Date: Fri, 8 Mar 2019 21:49:31 -0500 Subject: [PATCH] update section `pods are preempted unneccessarily` (#12961) Preemption must not happen when there is no pending Pod, or when the pending Pods have equal or lower priority than the victims. --- .../en/docs/concepts/configuration/pod-priority-preemption.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/configuration/pod-priority-preemption.md b/content/en/docs/concepts/configuration/pod-priority-preemption.md index 297c61f1a7..bcb1fab197 100644 --- a/content/en/docs/concepts/configuration/pod-priority-preemption.md +++ b/content/en/docs/concepts/configuration/pod-priority-preemption.md @@ -322,7 +322,7 @@ When a Pod is preempted, there will be events recorded for the preempted Pod. Preemption should happen only when a cluster does not have enough resources for a Pod. In such cases, preemption happens only when the priority of the pending Pod (preemptor) is higher than the victim Pods. Preemption must not happen when -there is no pending Pod, or when the pending Pods have equal or higher priority +there is no pending Pod, or when the pending Pods have equal or lower priority than the victims. If preemption happens in such scenarios, please file an issue. #### Pods are preempted, but the preemptor is not scheduled