A building-permits platform sees Pod counts thrash up and down under bursty traffic while HPA is enabled. What scale-down awareness should admins apply?
Select an answer to reveal the explanation.
Short Explanation
Bursty traffic can make the replica count yo-yo. Stabilization windows are the shock absorbers—HPA can wait before scale-down so you do not thrash Pods on every blip.
Full Explanation
HorizontalPodAutoscaler behavior includes scale-down stabilization and related controls so replica counts do not flap on short-lived metric spikes. HPA can and does scale down when metrics allow; disabling kube-proxy or inventing Service maxUnavailable settings is not how operators address HPA thrash.