Back to all scenarios
Scenario #412
Scaling & Load
Kubernetes v1.23, GKE
ReplicaSet Misalignment Led to Excessive Scale-Out
A stale ReplicaSet with label mismatches caused duplicate pod scale-out.
Find this helpful?
What Happened
Deployment scaled twice the required pod count after an upgrade.
Diagnosis Steps
- 1kubectl get replicasets showed multiple active sets with overlapping match labels.
- 2Pod count exceeded expected limits.
Root Cause
A new deployment overlapped labels with an old one ; HPA acted on both.
Fix/Workaround
• Cleaned up old ReplicaSets.
• Scoped matchLabels more tightly.
Lessons Learned
Label discipline is essential for reliable scaling.
How to Avoid
- 1Use distinct labels per version or release.
- 2Automate cleanup of unused ReplicaSets.