Skip to content
Permalink
Browse files

Updated horizontal-pod-autoscale.md file with newer command names. (#…

…13519)

HPA command names updated to --horizontal-pod-autoscaler-downscale-stabilization in the document.
  • Loading branch information...
paulsubrata55 authored and k8s-ci-robot committed Apr 10, 2019
1 parent ffa2996 commit bd8721baad54808058679153f4febd34efd3c380
Showing with 2 additions and 2 deletions.
  1. +2 −2 content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
@@ -161,7 +161,7 @@ from the metrics APIs), scaling is skipped.

Finally, just before HPA scales the target, the scale recommendation is recorded. The
controller considers all recommendations within a configurable window choosing the
highest recommendation from within that window. This value can be configured using the `--horizontal-pod-autoscaler-downscale-stabilization-window` flag, which defaults to 5 minutes.
highest recommendation from within that window. This value can be configured using the `--horizontal-pod-autoscaler-downscale-stabilization` flag, which defaults to 5 minutes.
This means that scaledowns will occur gradually, smoothing out the impact of rapidly
fluctuating metric values.

@@ -216,7 +216,7 @@ 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
upscale delay.

- `--horizontal-pod-autoscaler-downscale-delay`: The value for this option is a
- `--horizontal-pod-autoscaler-downscale-stabilization`: The value for this option is a
duration that specifies how long the autoscaler has to wait before another
downscale operation can be performed after the current one has completed.
The default value is 5 minutes (`5m0s`).

0 comments on commit bd8721b

Please sign in to comment.
You can’t perform that action at this time.