Adding missing info (cooldown period clarification) #127571
Open
+2
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hi, I'm an app services support engineer in Microsoft CSS. Received a customer case where they were anxious and confused about the cool down period behavior causing unexpected scaling actions (2508220050001316). Adding this clarification to the Microsoft docs will help prevent such confusion and support requests by clearly explaining when and how the cool down period works in Azure Container Apps scaling.
|
@AnkushRaj15 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 63cb801: ✅ Validation status: passed
For more details, please refer to the build report. |
| @@ -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. | |||
There was a problem hiding this comment.
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. |
|
@craigshoemaker - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I'm an app services support engineer in Microsoft CSS.
Received a customer case where they were anxious and confused about the cool down period behavior causing unexpected scaling actions (2508220050001316).
Adding this clarification to the Microsoft docs will help prevent such confusion and support requests by clearly explaining when and how the cool down period works in Azure Container Apps scaling.