From 067ed2e5ec16a1b80195a6736fb55a5bf23f9886 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Giuseppe=20Crin=C3=B2?= Date: Wed, 29 Jun 2022 01:26:28 +0200 Subject: [PATCH] docs: fix logic explanation for scale down delay (#1562) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off: Giuseppe Crinò --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4c4605ab..f020acbf 100644 --- a/README.md +++ b/README.md @@ -719,7 +719,7 @@ With the above example, the webhook server scales `example-runners` by `1` repli Of note is the `HRA.spec.scaleUpTriggers[].duration` attribute. This attribute is used to calculate if the replica number added via the trigger is expired or not. On each reconciliation loop, the controller sums up all the non-expiring replica numbers from previous scale-up triggers. It then compares the summed desired replica number against the current replica number. If the summed desired replica number > the current number then it means the replica count needs to scale up. -As mentioned previously, the `scaleDownDelaySecondsAfterScaleOut` property has the final say still. If the latest scale-up time + the anti-flapping duration is later than the current time, it doesn’t immediately scale up and instead retries the calculation again later to see if it needs to scale yet. +As mentioned previously, the `scaleDownDelaySecondsAfterScaleOut` property has the final say still. If the latest scale-up time + the anti-flapping duration is later than the current time, it doesn’t immediately scale down and instead retries the calculation again later to see if it needs to scale yet. ---