Skip to content

Commit bee8fec

Browse files
dipesh-rawatTim Bannister
andauthored
Add minimum and maximum values for PriorityClass
Co-authored-by: Tim Bannister <[email protected]>
1 parent 4df5efb commit bee8fec

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ and it cannot be prefixed with `system-`.
6565
A PriorityClass object can have any 32-bit integer value smaller than or equal
6666
to 1 billion. This means that the range of values for a PriorityClass object is
6767
from -2147483648 to 1000000000 inclusive. Larger numbers are reserved for
68-
critical system Pods that should not normally be preempted or evicted. A cluster
68+
built-in PriorityClasses that represent critical system Pods. A cluster
6969
admin should create one PriorityClass object for each such mapping that they want.
7070

7171
PriorityClass also has two optional fields: `globalDefault` and `description`.

0 commit comments

Comments
 (0)