You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-autoscaling/2021-scale-from-zero/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -263,7 +263,7 @@ Additionally the `replicas: 0` state is problematic as updating a HPA object `mi
263
263
will be disabled for the resource, if it was `> 0`, HPA will continue with the new `minReplicas` value.
264
264
265
265
To resolve this issue the KEP is introducing an explicit `ScaledToZero` condition inside the `HorizontalPodAutoscalerStatus`. When `ScaledToZero=True` was recorded the HPA will scale
266
-
up a workload from `0 ~> 1` and otherwise maintain the current behavior of performing no change.
266
+
up a workload from `0 ~> 1` and remove the condition `ScaledToZero=True`. If the condition is not found, the HPA maintains the current behavior of performing no change.
267
267
268
268
When the HPA scales a workload from `1 ~> 0`, it records the `ScaledToZero=True` condition inside the status.
269
269
@@ -299,11 +299,11 @@ proposal will be implemented, this is the place to discuss them.
299
299
Add `ScaledToZero` as HPA `HorizontalPodAutoscalerConditionType`
300
300
301
301
```golang
302
-
303
302
const (
304
303
// ScaledToZero indicates that the HPA controller scaled the workload to zero.
0 commit comments