Back to all scenarios
Scenario #455
Scaling & Load
Kubernetes v1.25, Google Cloud

Unpredictable Pod Scaling During Cluster Autoscaler Event

Pod scaling was unpredictable during a Cluster Autoscaler event due to a sudden increase in node availability.

Find this helpful?
What Happened

When Cluster Autoscaler added new nodes to the cluster, the autoscaling process became erratic as new pods were scheduled in unpredictable order.

Diagnosis Steps
  • 1Analyzed scaling logs and found that new nodes were provisioned, but pod scheduling was not coordinated well with available node resources.
  • 2Observed that new pods were not placed efficiently on the newly provisioned nodes.
Root Cause

Cluster Autoscaler was adding new nodes too quickly without proper scheduling coordination.

Fix/Workaround
• Adjusted Cluster Autoscaler settings to delay node addition during scaling events.
• Tweaked pod scheduling policies to ensure new pods were placed on the most appropriate nodes.
Lessons Learned

Cluster Autoscaler should work more harmoniously with pod scheduling to ensure efficient scaling.

How to Avoid
  • 1Fine-tune Cluster Autoscaler settings to prevent over-rapid node provisioning.
  • 2Use more advanced scheduling policies to manage pod placement efficiently.