Clarify cooldownPeriod for Deployments. (kedacore#157)

preflightsiren · Apr 30, 2020 · 4244719 · 4244719
1 parent 5554e3a
commit 4244719
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/content/docs/concepts/scaling-deployments.md b/content/docs/concepts/scaling-deployments.md
@@ -71,7 +71,9 @@ This is the interval to check each trigger on. By default KEDA will check each t
   cooldownPeriod:  300 # Optional. Default: 300 seconds
 ```
 
-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 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-cooldown-delay).
 
 **Example:** wait 5 minutes after the last time KEDA checked the queue and it was empty. (this is obviously dependent on `pollingInterval`)