QoS class isn't used for out-of-resource handling rankings

[shannonxtreme]

Page: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#interactions-of-pod-priority-and-qos

The second paragraph needs clarity. The QoS class isn't actually used to calculate the pod eviction order, but can be used to estimate the order.

Suggested content

The kubelet uses Priority to order pods for out-of-resource eviction. You can use the QoS class to estimate the order in which pods are most likely to get evicted. The kubelet ranks pods for eviction based on the following factors:

1. Whether or not the pod resource usage exceeds the defined requests
2. The pod Priority
3. The amount of the pod's resource consumption relative to the defined requests

For more information, see [Evicting end-user pods].

Note: this will likely link to #27739 instead of the existing Out of Resource Handling topic.

/sig docs
/language en
/assign

[k8s-ci-robot]

@shannonxtreme: This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sftim]

/sig node

[shannonxtreme]

/triage accepted

eh, worth a shot

[k8s-ci-robot]

@shannonxtreme: The label triage/accepted cannot be applied. Only GitHub organization members can add the label.

In response to this:

/triage accepted

eh, worth a shot

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.