From 9510891f42e24f0ada1f8d2f395985396be1d3d4 Mon Sep 17 00:00:00 2001 From: Sean Malloy Date: Tue, 4 Feb 2020 23:17:40 -0600 Subject: [PATCH] Remove reference to critical-pod annotation from documentation Newer versions of k8s(>= 1.16) no longer support the critical-pod annotation. Setting the priorityClassName is the correct way to mark a pod as critical. https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1826d4175..8809e7d84 100644 --- a/README.md +++ b/README.md @@ -270,7 +270,7 @@ strategies: When the descheduler decides to evict pods from a node, it employs following general mechanism: -* Critical pods (with annotations scheduler.alpha.kubernetes.io/critical-pod) are never evicted. +* [Critical pods](https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/) (with priorityClassName set to system-cluster-critical or system-node-critical) are never evicted. * Pods (static or mirrored pods or stand alone pods) not part of an RC, RS, Deployment or Jobs are never evicted because these pods won't be recreated. * Pods associated with DaemonSets are never evicted.