Back to all scenarios
Scenario #476
Scaling & Load
Kubernetes v1.25, Azure AKS
Autoscaling Slow Due to Cloud Provider API Delay
Pod scaling was delayed due to cloud provider API delays during scaling events.
Find this helpful?
What Happened
Scaling actions were delayed because the cloud provider API took longer than expected to provision new resources, affecting pod scheduling.
Diagnosis Steps
- 1Checked the scaling event logs and found that new nodes were being provisioned slowly due to API rate limiting.
- 2Observed delayed pod scheduling as a result of slow node availability.
Root Cause
Slow cloud provider API response times and rate limiting.
Fix/Workaround
• Worked with the cloud provider to optimize node provisioning time.
• Increased API limits to accommodate the scaling operations.
Lessons Learned
Cloud infrastructure API response time can impact scaling performance.
How to Avoid
- 1Ensure that the cloud provider API is optimized and scalable.
- 2Work with the provider to avoid rate limits during scaling events.