Kubernetes assigns a Pod to the BestEffort quality-of-service class when none of its containers define resource requests or limits. Kubernetes can schedule these Pods wherever it chooses, but this is the lowest QoS class and is generally unsuitable for dependable workloads. section 5.1.2
Best-effort placement has direct reliability consequences:
- During resource contention, Kubernetes considers BestEffort Pods first for eviction because they have no resource requests. section 5.1.3
- Among same-priority BestEffort Pods, Kubernetes starts with the Pods using the most resources. section 5.1.3
- Frequent Evicted statuses indicate that containers should request more resources and that cluster capacity may need review. section 5.1.3
An unreserved Pod
A Pod whose containers omit both requests and limits is classified as BestEffort. It may run on available nodes under normal conditions, but resource pressure makes it the first QoS class considered for eviction. section 5.1.2 section 5.1.3
Use the eviction-order figure to compare how BestEffort Pods are ranked against other Pods with equal priority. section 5.1.3
