Guaranteed Scheduling For Critical Add-On Pods task does not link to details of built in PriorityClasses

[aceeric]

Folks - on this page, regarding this language: "To mark a Pod as critical, set priorityClassName for that Pod to system-cluster-critical or system-node-critical. system-node-critical is the highest available priority, even higher than system-cluster-critical." This immediately brings to mind the question: "what do you mean by even higher, i.e. what is the effect?" A little searching yields this documentation which answers the question nicely. Consider adding some clarification on the effect of node vs cluster priority in your docs.

[sftim]

/retitle Guaranteed Scheduling For Critical Add-On Pods task does not link to details of built in PriorityClasses

We could and should update https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass to incorporate details about the built-in priority classes.

It is OK to copy text verbatim from https://kubernetes.io/blog/2023/01/12/protect-mission-critical-pods-priorityclass/ and you can also use your own wording.

/language en /help /triage accepted /priority backlog

[k8s-ci-robot]

@sftim: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/kubernetes/website/issues/39000): >/retitle Guaranteed Scheduling For Critical Add-On Pods task does not link to details of built in PriorityClasses > >We could and should update https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass to incorporate details about the built-in priority classes. > >It is OK to copy text verbatim from https://kubernetes.io/blog/2023/01/12/protect-mission-critical-pods-priorityclass/ and you can also use your own wording. > >/language en >/help >/triage accepted >/priority backlog Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[sftim]

We should also update https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/ to link to https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass once we update it.

[rajeshdeshpande02]

I am working on this issue. /assign

[vaibhav2107]

@rajeshdeshpande02 Are you still working on this issue

[vaibhav2107]

Unassigning @rajeshdeshpande02 as didn't receive any updates. Please assign if you get back to this or anyone can also assign to this issue /unassign @rajeshdeshpande02

[vaibhav2107]

/assign I would like to work on this issue