How does Kubernetes assign Guaranteed, Burstable, or BestEffort QoS to a Pod based on container requests and limits?
Select an answer to reveal the explanation.
Short Explanation
QoS is the eviction VIP line based on how carefully you filled in requests and limits. Match them for Guaranteed, leave them blank for BestEffort, and land in Burstable for the in-between cases. Probes do not pick the class.
Full Explanation
A Pod is Guaranteed when every container has CPU and memory requests equal to their limits (and those values are set). A Pod with no requests or limits is BestEffort. Any other mix yields Burstable. QoS influences eviction order under node memory pressure and is derived from the resources configuration, not from probes or PriorityClass alone.