Skip to content

Adding missing info (cooldown period clarification) #127571

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Adding missing info (cooldown period clarification) #127571

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions articles/container-apps/scale-app.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -317,6 +317,8 @@ Not supported in the Azure portal. Use the [Azure CLI](scale-app.md?pivots=azure

You can create a custom Container Apps scaling rule based on any [ScaledObject](https://keda.sh/docs/latest/concepts/scaling-deployments/)-based [KEDA scaler](https://keda.sh/docs/latest/scalers/) with these defaults:

**Note:** The KEDA cooldownPeriod only applies when scaling down to 0 instances and is not enforced for scale-down operations where the number of replicas decreases from N to a value greater than 0; whereas scaling up from 1 to N replicas is managed by the Kubernetes Horizontal Pod Autoscaler.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Note:** The KEDA cooldownPeriod only applies when scaling down to 0 instances and is not enforced for scale-down operations where the number of replicas decreases from N to a value greater than 0; whereas scaling up from 1 to N replicas is managed by the Kubernetes Horizontal Pod Autoscaler.
> [!NOTE]
> The KEDA cooldownPeriod only applies when scaling down to 0 instances and is not enforced for scale-down operations where the number of replicas decreases from N to a value greater than 0; whereas scaling up from 1 to N replicas is managed by the Kubernetes Horizontal Pod Autoscaler.


| Defaults | Seconds |
|--|--|
| Polling interval | 30 |
Expand Down