kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add minimum and maximum values for PriorityClass 

Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
Dipesh Rawat 2023-02-23 17:39:00 +00:00 committed by GitHub
parent 4df5efbaea
commit bee8feccc2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -65,7 +65,7 @@ and it cannot be prefixed with `system-`.
A PriorityClass object can have any 32-bit integer value smaller than or equal A PriorityClass object can have any 32-bit integer value smaller than or equal
to 1 billion. This means that the range of values for a PriorityClass object is to 1 billion. This means that the range of values for a PriorityClass object is
from -2147483648 to 1000000000 inclusive. Larger numbers are reserved for from -2147483648 to 1000000000 inclusive. Larger numbers are reserved for
critical system Pods that should not normally be preempted or evicted. A cluster built-in PriorityClasses that represent critical system Pods. A cluster
admin should create one PriorityClass object for each such mapping that they want. admin should create one PriorityClass object for each such mapping that they want.
PriorityClass also has two optional fields: `globalDefault` and `description`. PriorityClass also has two optional fields: `globalDefault` and `description`.