fix(k8s): add scaleUp/scaleDown stabilization to schemas HPA #844

Merged
argoyle merged 1 commits from tune-hpa-behavior into main 2026-05-21 17:10:19 +00:00
Showing only changes of commit eefab471d6 - Show all commits
+20
View File
@@ -18,3 +18,23 @@ spec:
target:
type: Utilization
averageUtilization: 60
behavior:
scaleUp:
# Wait 2min of sustained high CPU before scaling up. Schemas is
# event-driven and the per-request work is bursty even with the
# cache + warmup, so single spikes shouldn't pull replicas up.
stabilizationWindowSeconds: 120
policies:
- type: Pods
value: 1
periodSeconds: 60
scaleDown:
# Default 300s window kept pods pinned at maxReplicas long after
# the triggering spike had subsided. 120s is long enough to avoid
# flapping but lets the deployment return to minReplicas quickly
# once the workload calms.
stabilizationWindowSeconds: 120
policies:
- type: Pods
value: 1
periodSeconds: 60