Back to all scenarios
Scenario #434
Scaling & Load
Kubernetes v1.24, AWS EKS
Service Disruption During Auto-Scaling of StatefulSet
StatefulSet failed to scale properly during maintenance, causing service disruption.
Find this helpful?
What Happened
StatefulSet pods failed to scale correctly during a rolling update due to scaling policies not considering pod states.
Diagnosis Steps
- 1Logs revealed pods were stuck in a Pending state during scale-up.
- 2StatefulSet's rollingUpdate strategy wasn’t optimal.
Root Cause
StatefulSet scaling wasn’t fully compatible with the default rolling update strategy.
Fix/Workaround
• Tuning the rollingUpdate strategy allowed pods to scale without downtime.Lessons Learned
StatefulSets require special handling during scale-up or down.
How to Avoid
- 1Test scaling strategies with StatefulSets to avoid disruption.
- 2Use strategies suited for the application type.