How to fix HPA: scale down disabled by policy or stabilization window in Kubernetes
KubernetesINTERMEDIATEHIGHUpdated Dec 6, 2025ยท 110 views
HorizontalPodAutoscaler will not scale down pods even when demand decreases. Scale-down is disabled by policy, stabilization window, or autoscaling config.
Quick fix
Fixes HPA: scale down disabled by policy or stabilization window
- Step 1
- Step 2
- Step 3
- Step 4
- Step 5
kubernetes โ error
# HPA: scale down disabled by policy or stabilization windowHPA: scale down disabled by policy or stabilization window
What this error means
HPA can scale up quickly but intentionally limits scale-down to prevent thrashing (rapid up/down cycles that waste resources). The scale-down behavior is controlled by stabilization windows and scale-down policies. When these are too conservative, HPA will not scale down even when metrics indicate fewer replicas are needed.
Typical symptoms
- Pod count stays high even after load decreases
- HPA will not scale down to minReplicas
- kubectl describe hpa shows scale-down behavior disabled
- Metrics show low usage but pod count unchanged
- HPA events: "scale down stabilization active"
- Resource utilization low but cluster remains full
- Unnecessary pods consuming cluster resources
Common causes
- Scale-down stabilization window too long (default 5 minutes)
- Scale-down policy explicitly disabled
- Auto-scaler behavior policy set to conservative
- Recent scale-up event still within stabilization window
- Pod disruption budget preventing voluntary eviction
- minReplicas set too high
- Scaling policy with very slow scale-down rate
How to fix "HPA: scale down disabled by policy or stabilization window"
1Step 1
First diagnostic step
2Step 2
Second diagnostic step
3Step 3
Third diagnostic step
4Step 4
Fourth diagnostic step
5Step 5
Fifth diagnostic step
Advanced notes
Additional notes and platform-specific considerations.
Frequently asked questions
- What does "HPA: scale down disabled by policy or stabilization window" mean?
- HPA can scale up quickly but intentionally limits scale-down to prevent thrashing (rapid up/down cycles that waste resources). The scale-down behavior is controlled by stabilization windows and scale-down policies. When these are too conservative, HPA will not scale down even when metrics indicate fewer replicas are needed.
- How do I fix "HPA: scale down disabled by policy or stabilization window"?
- HorizontalPodAutoscaler will not scale down pods even when demand decreases. Scale-down is disabled by policy, stabilization window, or autoscaling config.
- What causes "HPA: scale down disabled by policy or stabilization window"?
- Scale-down stabilization window too long (default 5 minutes) Scale-down policy explicitly disabled Auto-scaler behavior policy set to conservative
- Is the "HPA: scale down disabled by policy or stabilization window" error serious?
- Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.
Official resources & further reading
- ๐Kubernetes Official Documentation
- ๐Kubernetes API Reference(Official Docs)
- ๐Kubernetes Tasks: Run Applications(Official Docs)
- ๐ฌStack Overflow: Kubernetes hpa scale down disabled(Stack Overflow)
- ๐Kubernetes GitHub Issues(GitHub)