From fa238ce550200189075876e3ef97b6b6bf66c99a Mon Sep 17 00:00:00 2001 From: rickbrouwer Date: Fri, 25 Oct 2024 21:23:01 +0200 Subject: [PATCH] Fix link for coolDownPeriod (#1491) Signed-off-by: Rick Brouwer --- content/docs/1.4/concepts/scaling-deployments.md | 2 +- content/docs/1.5/concepts/scaling-deployments.md | 2 +- content/docs/2.0/concepts/scaling-deployments.md | 2 +- content/docs/2.1/concepts/scaling-deployments.md | 2 +- content/docs/2.10/concepts/scaling-deployments.md | 2 +- content/docs/2.11/concepts/scaling-deployments.md | 2 +- content/docs/2.12/concepts/scaling-deployments.md | 2 +- content/docs/2.13/concepts/scaling-deployments.md | 2 +- content/docs/2.14/concepts/scaling-deployments.md | 2 +- content/docs/2.14/reference/scaledobject-spec.md | 2 +- content/docs/2.15/reference/scaledobject-spec.md | 2 +- content/docs/2.16/reference/scaledobject-spec.md | 2 +- content/docs/2.2/concepts/scaling-deployments.md | 2 +- content/docs/2.3/concepts/scaling-deployments.md | 2 +- content/docs/2.4/concepts/scaling-deployments.md | 2 +- content/docs/2.5/concepts/scaling-deployments.md | 2 +- content/docs/2.6/concepts/scaling-deployments.md | 2 +- content/docs/2.7/concepts/scaling-deployments.md | 2 +- content/docs/2.8/concepts/scaling-deployments.md | 2 +- content/docs/2.9/concepts/scaling-deployments.md | 2 +- 20 files changed, 20 insertions(+), 20 deletions(-) diff --git a/content/docs/1.4/concepts/scaling-deployments.md b/content/docs/1.4/concepts/scaling-deployments.md index 8f719beb1..60505ae36 100644 --- a/content/docs/1.4/concepts/scaling-deployments.md +++ b/content/docs/1.4/concepts/scaling-deployments.md @@ -73,7 +73,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the deployment back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment`, KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment`, KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/1.5/concepts/scaling-deployments.md b/content/docs/1.5/concepts/scaling-deployments.md index 2e9f99a7a..de3a5f842 100644 --- a/content/docs/1.5/concepts/scaling-deployments.md +++ b/content/docs/1.5/concepts/scaling-deployments.md @@ -73,7 +73,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the deployment back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment`, KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment`, KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.0/concepts/scaling-deployments.md b/content/docs/2.0/concepts/scaling-deployments.md index c7c7a509c..87c86e2a8 100644 --- a/content/docs/2.0/concepts/scaling-deployments.md +++ b/content/docs/2.0/concepts/scaling-deployments.md @@ -99,7 +99,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.1/concepts/scaling-deployments.md b/content/docs/2.1/concepts/scaling-deployments.md index 4ac5c07c5..81c92ddb9 100644 --- a/content/docs/2.1/concepts/scaling-deployments.md +++ b/content/docs/2.1/concepts/scaling-deployments.md @@ -99,7 +99,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.10/concepts/scaling-deployments.md b/content/docs/2.10/concepts/scaling-deployments.md index 44bd1e1e6..1538286b4 100644 --- a/content/docs/2.10/concepts/scaling-deployments.md +++ b/content/docs/2.10/concepts/scaling-deployments.md @@ -102,7 +102,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.11/concepts/scaling-deployments.md b/content/docs/2.11/concepts/scaling-deployments.md index 866eb3a79..7d65f8495 100644 --- a/content/docs/2.11/concepts/scaling-deployments.md +++ b/content/docs/2.11/concepts/scaling-deployments.md @@ -105,7 +105,7 @@ This is the interval to check each trigger on. By default KEDA will check each t The period to wait after the last trigger reported active before scaling the resource back to 0. By default it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.12/concepts/scaling-deployments.md b/content/docs/2.12/concepts/scaling-deployments.md index a9f834f33..ec84a024a 100644 --- a/content/docs/2.12/concepts/scaling-deployments.md +++ b/content/docs/2.12/concepts/scaling-deployments.md @@ -106,7 +106,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.13/concepts/scaling-deployments.md b/content/docs/2.13/concepts/scaling-deployments.md index a4a5e63d5..276bca628 100644 --- a/content/docs/2.13/concepts/scaling-deployments.md +++ b/content/docs/2.13/concepts/scaling-deployments.md @@ -106,7 +106,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.14/concepts/scaling-deployments.md b/content/docs/2.14/concepts/scaling-deployments.md index cd2f23c06..ad225062d 100644 --- a/content/docs/2.14/concepts/scaling-deployments.md +++ b/content/docs/2.14/concepts/scaling-deployments.md @@ -107,7 +107,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.14/reference/scaledobject-spec.md b/content/docs/2.14/reference/scaledobject-spec.md index 0e7e11023..1591c99d3 100644 --- a/content/docs/2.14/reference/scaledobject-spec.md +++ b/content/docs/2.14/reference/scaledobject-spec.md @@ -82,7 +82,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0, in seconds. By default, it's 300 (5 minutes). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/../concepts/scaling-deployments.md#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.15/reference/scaledobject-spec.md b/content/docs/2.15/reference/scaledobject-spec.md index 124d02062..dd9b0f9b2 100644 --- a/content/docs/2.15/reference/scaledobject-spec.md +++ b/content/docs/2.15/reference/scaledobject-spec.md @@ -83,7 +83,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0, in seconds. By default, it's 300 (5 minutes). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/../concepts/scaling-deployments.md#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.16/reference/scaledobject-spec.md b/content/docs/2.16/reference/scaledobject-spec.md index 124d02062..dd9b0f9b2 100644 --- a/content/docs/2.16/reference/scaledobject-spec.md +++ b/content/docs/2.16/reference/scaledobject-spec.md @@ -83,7 +83,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0, in seconds. By default, it's 300 (5 minutes). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/../concepts/scaling-deployments.md#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.2/concepts/scaling-deployments.md b/content/docs/2.2/concepts/scaling-deployments.md index 4ac5c07c5..81c92ddb9 100644 --- a/content/docs/2.2/concepts/scaling-deployments.md +++ b/content/docs/2.2/concepts/scaling-deployments.md @@ -99,7 +99,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.3/concepts/scaling-deployments.md b/content/docs/2.3/concepts/scaling-deployments.md index 4ac5c07c5..81c92ddb9 100644 --- a/content/docs/2.3/concepts/scaling-deployments.md +++ b/content/docs/2.3/concepts/scaling-deployments.md @@ -99,7 +99,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.4/concepts/scaling-deployments.md b/content/docs/2.4/concepts/scaling-deployments.md index d1f2fcd52..77365680a 100644 --- a/content/docs/2.4/concepts/scaling-deployments.md +++ b/content/docs/2.4/concepts/scaling-deployments.md @@ -103,7 +103,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.5/concepts/scaling-deployments.md b/content/docs/2.5/concepts/scaling-deployments.md index 8c7bd084c..a5c1c843c 100644 --- a/content/docs/2.5/concepts/scaling-deployments.md +++ b/content/docs/2.5/concepts/scaling-deployments.md @@ -103,7 +103,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.6/concepts/scaling-deployments.md b/content/docs/2.6/concepts/scaling-deployments.md index 8c7bd084c..a5c1c843c 100644 --- a/content/docs/2.6/concepts/scaling-deployments.md +++ b/content/docs/2.6/concepts/scaling-deployments.md @@ -103,7 +103,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.7/concepts/scaling-deployments.md b/content/docs/2.7/concepts/scaling-deployments.md index 6897165af..543ce6376 100644 --- a/content/docs/2.7/concepts/scaling-deployments.md +++ b/content/docs/2.7/concepts/scaling-deployments.md @@ -101,7 +101,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.8/concepts/scaling-deployments.md b/content/docs/2.8/concepts/scaling-deployments.md index b02d7095f..44ca45e89 100644 --- a/content/docs/2.8/concepts/scaling-deployments.md +++ b/content/docs/2.8/concepts/scaling-deployments.md @@ -102,7 +102,7 @@ This is the interval to check each trigger on. By default, KEDA will check each The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`) diff --git a/content/docs/2.9/concepts/scaling-deployments.md b/content/docs/2.9/concepts/scaling-deployments.md index c1ffdfcef..69a65ab3b 100644 --- a/content/docs/2.9/concepts/scaling-deployments.md +++ b/content/docs/2.9/concepts/scaling-deployments.md @@ -102,7 +102,7 @@ This is the interval to check each trigger on. By default KEDA will check each t The period to wait after the last trigger reported active before scaling the resource back to 0. By default, it's 5 minutes (300 seconds). -The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-cooldowndelay). +The `cooldownPeriod` only applies after a trigger occurs; when you first create your `Deployment` (or `StatefulSet`/`CustomResource`), KEDA will immediately scale it to `minReplicaCount`. Additionally, the KEDA `cooldownPeriod` only applies when scaling to 0; scaling from 1 to N replicas is handled by the [Kubernetes Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`)