Skip to content

Add actual priority values for built-in PriorityClasses to documentation #54107

@kfess

Description

@kfess

This is a Feature Request

What would you like to be added

Add the actual priority values for the built-in PriorityClasses (system-cluster-critical and system-node-critical) to the Pod Priority and Preemption page.

Why is this needed?

The current documentation mentions these built-in PriorityClasses but doesn't specify their actual priority values:

  • system-node-critical: 2000001000
  • system-cluster-critical: 2000000000

Users can see these values by running kubectl get priorityclasses, but having them in the documentation would provide better context when choosing right priority values for custom PriorityClasses.

If this is valuable,
/assign

Metadata

Metadata

Assignees

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.language/enIssues or PRs related to English languagepriority/backlogHigher priority than priority/awaiting-more-evidence.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions