We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 4df5efb commit bee8fecCopy full SHA for bee8fec
content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md
@@ -65,7 +65,7 @@ and it cannot be prefixed with `system-`.
65
A PriorityClass object can have any 32-bit integer value smaller than or equal
66
to 1 billion. This means that the range of values for a PriorityClass object is
67
from -2147483648 to 1000000000 inclusive. Larger numbers are reserved for
68
-critical system Pods that should not normally be preempted or evicted. A cluster
+built-in PriorityClasses that represent critical system Pods. A cluster
69
admin should create one PriorityClass object for each such mapping that they want.
70
71
PriorityClass also has two optional fields: `globalDefault` and `description`.
0 commit comments