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
@@ -231,7 +231,7 @@ The "Design Details" section below is for the real
231
231
nitty-gritty.
232
232
-->
233
233
234
-
Allow the HPA to scale from and to zero using `minReplicas: 0`when explicitly enabled with a flag.
234
+
Allow the HPA to scale from and to zero using `minReplicas: 0`and a HPA status condition.
235
235
236
236
### User Stories (Optional)
237
237
@@ -262,7 +262,7 @@ As `replicas: 0` is now a possible state when using `minReplicas: 0` it can no l
262
262
Additionally the `replicas: 0` state is problematic as updating a HPA object `minReplicas` from `0` to `1` has different behavior. If `replicas` was `0` during the update, HPA
263
263
will be disabled for the resource, if it was `> 0`, HPA will continue with the new `minReplicas` value.
264
264
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
265
+
To resolve these issues the KEP is introducing an explicit `ScaledToZero` condition inside the `HorizontalPodAutoscalerStatus`. When `ScaledToZero=True` was recorded the HPA will scale
266
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.
0 commit comments