Back to all scenarios
Scenario #429
Scaling & Load
Kubernetes v1.24, on-prem
Resource Constraints on Node Impacted Pod Scaling
Pod scaling failed due to resource constraints on nodes during high load.
Find this helpful?
What Happened
Autoscaler triggered, but nodes lacked available resources, preventing new pods from starting.
Diagnosis Steps
- 1kubectl describe nodes showed resource exhaustion.
- 2kubectl get pods confirmed that scaling requests were blocked.
Root Cause
Nodes were running out of resources during scaling decisions.
Fix/Workaround
• Added more nodes to the cluster.
• Increased resource limits for node pools.Lessons Learned
Cluster resource provisioning must be aligned with scaling needs.
How to Avoid
- 1Regularly monitor node resource usage.
- 2Use cluster autoscaling to add nodes as needed.