How to fix HPA: scale down disabled by policy or stabilization window in Kubernetes

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

1. Scale-down stabilization window too long (default 5 minutes)
2. Scale-down policy explicitly disabled
3. Auto-scaler behavior policy set to conservative
4. Recent scale-up event still within stabilization window
5. Pod disruption budget preventing voluntary eviction
6. minReplicas set too high
7. Scaling policy with very slow scale-down rate

How to fix "HPA: scale down disabled by policy or stabilization window"

Advanced notes

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.

Related errors

• ScaleTargetRef not found

  How to fix "ScaleTargetRef not found" in Kubernetes HPA

  HIGH

• missing request for cpu in container

  How to fix "missing request for cpu in container" in Kubernetes HPA

  HIGH

• unable to compute replica count

  How to fix "unable to compute replica count" in Kubernetes HPA

  MEDIUM

• failed to get cpu utilization: unable to get metrics

  How to fix "failed to get cpu utilization: unable to get metrics" in Kubernetes

  MEDIUM

• upstream connect error or disconnect/reset before headers. reset reason: overflow

  How to fix "upstream connect error or disconnect/reset before headers" in Kubernetes

  HIGH

• Waiting for rollout to finish

  How to fix "Waiting for rollout to finish" in Kubernetes

  HIGH

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)