Add priority values for built-in PriorityClasses#56444
Conversation
|
|
|
Welcome @mmustafasenoglu! |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi! The prow bot flagged the commit message because it contains To fix this, you need to amend the commit message and force push: git checkout fix/add-priority-values
git commit --amend -m "Add priority values for built-in PriorityClasses
Add the actual priority values for system-node-critical (2000001000)
and system-cluster-critical (2000000000) to the Pod Priority and
Preemption documentation page.
Related: #54107"
git push --forceThis replaces |
Add the actual priority values for system-node-critical (2000001000) and system-cluster-critical (2000000000) to the Pod Priority and Preemption documentation page. Related: kubernetes#54107
cd63b12 to
0ad55a1
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
What this PR does
Adds the actual priority values for the built-in PriorityClasses to the Pod Priority and Preemption documentation page.
Changes
Why
The current documentation mentions these built-in PriorityClasses but doesn't specify their actual priority values. Users can see these values by running , but having them in the documentation provides better context when choosing priority values for custom PriorityClasses.
Fixes #54107