From 9996602345a2bec91581b2a751e19b39b23c78e8 Mon Sep 17 00:00:00 2001 From: Guangya Liu Date: Tue, 11 Apr 2017 13:51:27 +0800 Subject: [PATCH] Updated doc for critical pod. Clarified that the rescheduler should be enabled by default as a static pod for critical pod. --- .../guaranteed-scheduling-critical-addon-pods.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/cluster-administration/guaranteed-scheduling-critical-addon-pods.md b/docs/concepts/cluster-administration/guaranteed-scheduling-critical-addon-pods.md index 6b08652013..627c3fe665 100644 --- a/docs/concepts/cluster-administration/guaranteed-scheduling-critical-addon-pods.md +++ b/docs/concepts/cluster-administration/guaranteed-scheduling-critical-addon-pods.md @@ -39,8 +39,8 @@ killed for this purpose. ## Config -Rescheduler doesn't have any user facing configuration (component config) or API. -It's enabled by default. It can be disabled: +Rescheduler should be [enabled by default as a static pod](https://github.com/kubernetes/kubernetes/blob/master/cluster/saltbase/salt/rescheduler/rescheduler.manifest). +It doesn't have any user facing configuration (component config) or API and can be disabled: * during cluster setup by setting `ENABLE_RESCHEDULER` flag to `false` * on running cluster by deleting its manifest from master node