From d8252bbcc5b7f49ed89782c2f97a14e1dcadcf89 Mon Sep 17 00:00:00 2001 From: Piotr Betkier Date: Fri, 3 Mar 2023 13:48:14 +0100 Subject: [PATCH] Clarify horizontal pod autoscaler docs on scaling behavior Stresses that behavior controls define limits to scaling (what at most can happen) and not the size of scaling actions verbatim. This is currently repeatedly being misunderstood by users. --- .../en/docs/tasks/run-application/horizontal-pod-autoscale.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 09c91f8780..f9ac9b65cd 100644 --- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md +++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md @@ -470,7 +470,7 @@ for scaling down which allows a 100% of the currently running replicas to be rem means the scaling target can be scaled down to the minimum allowed replicas. For scaling up there is no stabilization window. When the metrics indicate that the target should be scaled up the target is scaled up immediately. There are 2 policies where 4 pods or a 100% of the currently -running replicas will be added every 15 seconds till the HPA reaches its steady state. +running replicas may at most be added every 15 seconds till the HPA reaches its steady state. ### Example: change downscale stabilization window