Back to all scenarios
Scenario #58
Cluster Management
K8s v1.19, Bare Metal
Node Overcommitment Leading to Pod Evictions
Node overcommitment led to pod evictions, causing application downtime.
Find this helpful?
What Happened
Due to improper resource requests and limits, the node was overcommitted, which led to the eviction of critical pods.
Diagnosis Steps
- 1Checked the node’s resource utilization and found it was maxed out.
- 2Analyzed pod logs to see eviction messages related to resource limits.
Root Cause
Pods did not have properly set resource requests and limits, leading to resource overcommitment on the node.
Fix/Workaround
• Added appropriate resource requests and limits to the affected pods.
• Rescheduled the pods to other nodes with available resources.Lessons Learned
Properly setting resource requests and limits prevents overcommitment and avoids pod evictions.
How to Avoid
- 1Always set appropriate resource requests and limits for all pods.
- 2Use resource quotas and limit ranges to prevent overcommitment.