Skip to content

Commit 5785bfd

Browse files
Feedback
1 parent 6cc5361 commit 5785bfd

File tree

1 file changed

+2
-2
lines changed
  • keps/sig-autoscaling/2021-scale-from-zero

1 file changed

+2
-2
lines changed

keps/sig-autoscaling/2021-scale-from-zero/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ The "Design Details" section below is for the real
231231
nitty-gritty.
232232
-->
233233

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.
235235

236236
### User Stories (Optional)
237237

@@ -262,7 +262,7 @@ As `replicas: 0` is now a possible state when using `minReplicas: 0` it can no l
262262
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
263263
will be disabled for the resource, if it was `> 0`, HPA will continue with the new `minReplicas` value.
264264

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
266266
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.
267267

268268
When the HPA scales a workload from `1 ~> 0`, it records the `ScaledToZero=True` condition inside the status.

0 commit comments

Comments
 (0)