openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Example list of system-cluster-critical priority class is wrong

Browse Source
This commit is contained in:
Michael Burke
2019-07-22 13:14:51 -04:00
committed by openshift-cherrypick-robot
parent fd7ab8c779
commit aa40fb35d7
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
modules/nodes-pods-priority-about.adoc
View File

@@ -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