QoS Classes: The Eviction Order Nobody Chose
Kubernetes assigns a QoS class from requests/limits, never an explicit choice. A critical service with no limits gets evicted first.
Kubernetes assigns a QoS class from requests/limits, never an explicit choice. A critical service with no limits gets evicted first.
La classe QoS d'un pod fixe son ordre d'éviction, déduite des requests/limits, jamais choisie explicitement. Un service critique sans limits part en premier.
What actually happens when a pod crosses its CPU or memory limit, how QoS classes are derived, the no-limits debate, and a method to set sane defaults.
Ce qui se passe vraiment quand un pod Kubernetes dépasse sa limite CPU ou mémoire, les classes QoS, le débat des limites, et une méthode de réglage.