Back to all scenarios
Scenario #95
Cluster Management
K8s v1.20, AWS EKS
Node Pool Scaling Failure Due to Insufficient Quotas
Node pool scaling failed because the account exceeded resource quotas in AWS.
Find this helpful?
What Happened
When attempting to scale up a node pool, the scaling operation failed due to hitting AWS resource quotas.
Diagnosis Steps
- 1Reviewed the EKS and AWS console to identify quota limits.
- 2Found that the account had exceeded the EC2 instance limit for the region.
Root Cause
Insufficient resource quotas in the AWS account.
Fix/Workaround
• Requested a quota increase from AWS support.
• Once the request was approved, scaled the node pool successfully.Lessons Learned
Monitor cloud resource quotas to ensure scaling operations are not blocked.
How to Avoid
- 1Keep track of resource quotas and request increases in advance.
- 2Automate quota monitoring and alerting to avoid surprises during scaling.