From 57c9a5bba745a1ebe67f76db63171d24bf32482f Mon Sep 17 00:00:00 2001 From: RaviSantosh Gudimetla Date: Mon, 29 Jan 2018 11:32:26 -0500 Subject: [PATCH] "Updated the priorityClass changes" --- .../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 e8daab72b8..c992e26935 100644 --- a/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md +++ b/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md @@ -64,4 +64,4 @@ To be considered critical, the pod has to run in the `kube-system` namespace (co or -* have the `scheduler.alpha.kubernetes.io/critical-pod` annotation set to empty string(This will be deprecated too). +* have the `scheduler.alpha.kubernetes.io/critical-pod` annotation set to empty string(This will be deprecated too). This ensures that the pod gets "system-cluster-critical" priority.