From aa40fb35d77283f333d0838c0d8b98fb7eb5a712 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Mon, 22 Jul 2019 13:14:51 -0400 Subject: [PATCH] Example list of system-cluster-critical priority class is wrong --- modules/nodes-pods-priority-about.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/modules/nodes-pods-priority-about.adoc b/modules/nodes-pods-priority-about.adoc index 29c96413eb..5e0c510288 100644 --- a/modules/nodes-pods-priority-about.adoc +++ b/modules/nodes-pods-priority-about.adoc @@ -22,11 +22,7 @@ system-cluster-critical 2019-03-13T14:01:10Z system-node-critical 2019-03-13T14:01:10Z ---- -* *system-node-critical* - This priority class has a value of 2000001000 and is used for all pods that should never be evicted from a node. Examples of pods that have this priority class are `sdn-ovs`, `sdn`, and so forth. - -* *system-cluster-critical* - This priority class has a value of 2000000000 (two billion) and is used with pods that are important for the cluster. Pods with this priority class can be evicted from a node in certain circumstances. For example, pods configured with the `system-node-critical` priority class can take priority. However, this priority class does ensure guaranteed scheduling. Examples of pods that can have this priority class are fluentd, add-on components like descheduler, and so forth. -+ -A number of critical components include the `system-cluster-critical` priority class by default, for example: +* *system-node-critical* - This priority class has a value of 2000001000 and is used for all pods that should never be evicted from a node. Examples of pods that have this priority class are `sdn-ovs`, `sdn`, and so forth. A number of critical components include the `system-node-critical` priority class by default, for example: + ** master-api ** master-controller @@ -34,6 +30,10 @@ A number of critical components include the `system-cluster-critical` priority c ** sdn ** sdn-ovs ** sync + +* *system-cluster-critical* - This priority class has a value of 2000000000 (two billion) and is used with pods that are important for the cluster. Pods with this priority class can be evicted from a node in certain circumstances. For example, pods configured with the `system-node-critical` priority class can take priority. However, this priority class does ensure guaranteed scheduling. Examples of pods that can have this priority class are fluentd, add-on components like descheduler, and so forth. +A number of critical components include the `system-cluster-critical` priority class by default, for example: ++ ** fluentd ** metrics-server ** descheduler