fixes explanation for --[hpa]-stabilization
The current explanation is misleading (for example: for consistently decreasing resource usage, the HPA stabilization does not impact the frequency of its actuation). This has confused users recently ( https://github.com/kubernetes/kubernetes/issues/96671 )
This commit is contained in:
parent
65e4bede91
commit
3d23d1799b
|
@ -221,9 +221,9 @@ the global HPA settings exposed as flags for the `kube-controller-manager` compo
|
||||||
Starting from v1.12, a new algorithmic update removes the need for the
|
Starting from v1.12, a new algorithmic update removes the need for the
|
||||||
upscale delay.
|
upscale delay.
|
||||||
|
|
||||||
- `--horizontal-pod-autoscaler-downscale-stabilization`: The value for this option is a
|
- `--horizontal-pod-autoscaler-downscale-stabilization`: Specifies the duration of the
|
||||||
duration that specifies how long the autoscaler has to wait before another
|
downscale stabilization time window. Horizontal Pod Autoscaler remembers
|
||||||
downscale operation can be performed after the current one has completed.
|
the historical recommended sizes and only acts on the largest size within this time window.
|
||||||
The default value is 5 minutes (`5m0s`).
|
The default value is 5 minutes (`5m0s`).
|
||||||
|
|
||||||
{{< note >}}
|
{{< note >}}
|
||||||
|
|
Loading…
Reference in New Issue