Delay -> overshoot01
What: demand stays high while capacity boots, so successive observations request still more replicas. When capacity arrives, it may exceed need.
Observe: desired replicas climbing while Ready changes slowly; a later burst of endpoints.
Improve: headroom, faster startup, sane scale-up policies, scheduled capacity. Trade-off: cost or slower reaction.
Noisy signal -> oscillation02
What: replicas repeatedly scale up and down around a threshold.
Observe: alternating recommendations and frequent Pod churn.
Improve: stabilization windows, tolerance, less noisy aggregation. Trade-off: slower convergence.
Aggressive scale-down -> relapse03
What: a brief dip removes warm capacity; returning demand finds the service cold again.
Observe: latency spikes shortly after downscale, repeated cold starts.
Improve: conservative scale-down, minimum replicas, Pod disruption controls. Trade-off: idle spend.
Bad requests -> bad decisions04
What: CPU targets become misleading and scheduling may pack Pods unrealistically.
Observe: throttling, OOMs, Pending Pods, or surprising CPU utilization percentages.
Improve: measure and right-size requests; consider VPA recommendations. Trade-off: migration effort and possible restarts.
More clients -> dependency collapse05
What: each new replica opens pools and adds concurrency against an already slow database or API.
Observe: app replica count rises while DB connections, lock waits, errors, and retries rise faster.
Improve: global concurrency limits, backpressure, caching, query work, load shedding. Trade-off: queued or rejected work.
Scale-to-zero -> cold first request06
What: no worker exists when demand returns. A trigger must be observed before capacity starts.
Observe: queue growth or delayed first response during activation.
Improve: keep one warm replica for latency-critical paths, buffer work safely. Trade-off: baseline cost.
HPA behavior supports separate scale-up/down policies and stabilization windows. The default downscale stabilization window is five minutes; controller flags can change cluster defaults. Official behavior reference ↗