From effcc3db9448f3d58d27558d45578b3f567162ae Mon Sep 17 00:00:00 2001 From: RaviSantosh Gudimetla Date: Thu, 1 Feb 2018 10:57:05 -0500 Subject: [PATCH] Update guaranteed-scheduling-critical-addon-pods.md --- .../guaranteed-scheduling-critical-addon-pods.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md b/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md index 85db60f231..e1652edafc 100644 --- a/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md +++ b/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md @@ -41,7 +41,7 @@ while the other pods shouldn't tolerate the taint. The taint is removed once the *Warning:* currently there is no guarantee which node is chosen and which pods are being killed in order to schedule critical pods, so if rescheduler is enabled your pods might be occasionally -killed for this purpose. Please ensure that rescheduler is enabled along with priorities & preemptions in default-scheduler as it may have unwanted side-effects. +killed for this purpose. Please ensure that rescheduler is not enabled along with priorities & preemptions in default-scheduler as rescheduler is oblivious to priorities and it may evict high priority pods, instead of low priority ones. ## Config