From 753f57f0e68640c2a73010ed76e4b83a248d2837 Mon Sep 17 00:00:00 2001 From: nownabe Date: Fri, 12 Oct 2018 22:21:18 +0900 Subject: [PATCH] Tweak Horizontal Pod Autoscaler documentation (#10596) * Use consistent terms * Fix typo --- .../en/docs/tasks/run-application/horizontal-pod-autoscale.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md index d2cc4003db..1c1cbd0a5e 100644 --- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md +++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md @@ -141,7 +141,7 @@ the magnitude of any potential scale. Furthermore, if any not-yet-ready pods were present, and we would have scaled up without factoring in missing metrics or not-yet-ready pods, we -conservatively assume the non-yet-ready pods are consuming 0% of the +conservatively assume the not-yet-ready pods are consuming 0% of the desired metric, further dampening the magnitude of a scale up. After factoring in the not-yet-ready pods and missing metrics, we @@ -163,7 +163,7 @@ from the metrics APIs), scaling is skipped. Finally, just before HPA scales the target, the scale reccomendation 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. -This means that scaledowns will occur gradually, smothing out the impact of rapidly +This means that scaledowns will occur gradually, smoothing out the impact of rapidly fluctuating metric values. ## API Object