Skip to content

Commit 8edace4

Browse files
Refine two points.
1 parent c2abdab commit 8edace4

File tree

1 file changed

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

1 file changed

+3
-2
lines changed

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -661,7 +661,7 @@ Longer term, we may want to require automated upgrade/rollback tests, but we
661661
are missing a bunch of machinery and tooling and can't do that now.
662662
-->
663663

664-
No yet as no implementation is available.
664+
No yet as no implementation based on the new condition is available.
665665

666666
###### Is the rollout accompanied by any deprecations and/or removals of features, APIs, fields of API types, flags, etc.?
667667

@@ -688,7 +688,8 @@ checking if there are objects with field X set) may be a last resort. Avoid
688688
logs or events for this purpose.
689689
-->
690690

691-
The feature is used if workloads are scaled to zero by the autoscaling controller.
691+
The new status will be visible inside the `kube_horizontalpodautoscaler_status_condition` metric provided by [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics) as
692+
and the `minReplicas: 0` setting reflected in `kube_horizontalpodautoscaler_spec_min_replicas`.
692693

693694
###### How can someone using this feature know that it is working for their instance?
694695

0 commit comments

Comments
 (0)