From 8c7015d4fad1685baea2838b0f4c1172e18aa695 Mon Sep 17 00:00:00 2001 From: Stewart-YU Date: Sun, 3 Sep 2017 10:22:26 +0800 Subject: [PATCH] Update guaranteed-scheduling-critical-addon-pods.md Fix format: make note multiline. --- .../guaranteed-scheduling-critical-addon-pods.md | 1 + 1 file changed, 1 insertion(+) 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 de939aafb6..4bcef76e6e 100644 --- a/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md +++ b/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md @@ -49,6 +49,7 @@ It doesn't have any user facing configuration (component config) or API and can ### Marking add-on as critical To be critical an add-on has to run in `kube-system` namespace (configurable via flag) and + * have the `scheduler.alpha.kubernetes.io/critical-pod` annotation set to empty string, and * have the PodSpec's `tolerations` field set to `[{"key":"CriticalAddonsOnly", "operator":"Exists"}]`