Back to all scenarios
Scenario #91
Cluster Management
K8s v1.20, AWS EKS
Resource Starvation Due to Over-provisioned Pods
Resource starvation occurred on nodes because pods were over-provisioned, consuming more resources than expected.
Find this helpful?
What Happened
Pods were allocated more resources than necessary, causing resource contention on the nodes.
Diagnosis Steps
- 1Analyzed node and pod resource utilization.
- 2Found that the CPU and memory resources for several pods were unnecessarily high, leading to resource starvation for other pods.
Root Cause
Incorrect resource requests and limits set for the pods, causing resource over-allocation.
Fix/Workaround
• Reduced resource requests and limits based on actual usage metrics.
• Re-deployed the pods with optimized resource configurations.
Lessons Learned
Accurate resource requests and limits should be based on actual usage data.
How to Avoid
- 1Regularly monitor resource utilization and adjust requests/limits accordingly.
- 2Use vertical pod autoscalers for better resource distribution.