You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Msg":"Replica 'my-container-app--00001111-aaaaa22222-bbbb' has been scheduled to run on a node.",
261
261
"Reason":"AssigningReplica",
262
262
"EventSource":"ContainerAppController",
263
263
"Count":0
@@ -297,17 +297,20 @@ The following screenshot shows a zoomed view of how the requests received by you
297
297
298
298
## CPU and memory scaling
299
299
300
-
You should prefer [HTTP scale rules](/azure/container-apps/scale-app#http) to CPU or memory scale rules when possible.
301
-
302
-
When you use the Azure CLI to add a scale rule to a container app that already has a scale rule, the new scale rule replaces the old scale rule. To see how to add multiple scale rules, see [Multiple scale rules](#multiple-scale-rules).
300
+
You should prefer [HTTP scale rules](/azure/container-apps/scale-app#http) to CPU or memory scale rules when possible. CPU and memory scaling don't allow your container app to scale to zero.
303
301
304
302
After you add a CPU or memory scale rule, you can test it by [sending requests to your container app](#send-requests) and [viewing the scaling in Azure portal](#view-scaling-in-azure-portal-optional).
305
303
306
304
### CPU scaling
307
305
308
-
CPU scaling allows your app to scale in or out depending on how much the CPU is being used. CPU scaling doesn't allow your container app to scale to 0. For more information about this trigger, see [KEDA CPU scale trigger](https://keda.sh/docs/scalers/cpu/).
306
+
CPU scaling allows your app to scale in or out depending on how much the CPU is being used. CPU scaling doesn't allow your container app to scale to zero. For more information about this trigger, see [KEDA CPU scale trigger](https://keda.sh/docs/scalers/cpu/).
307
+
308
+
Add a CPU scale rule to your container app by running the `az containerapp update` command.
309
+
310
+
> [!NOTE]
311
+
> When you use the Azure CLI to add a scale rule to a container app that already has a scale rule, the new scale rule replaces the old scale rule. To see how to add multiple scale rules, see [Multiple scale rules](#multiple-scale-rules).
309
312
310
-
Add a CPU scale rule to your container app by running the `az containerapp update`command. Replace the `<PLACEHOLDERS>` with your values. The CPU utilization value is the percentage of CPU utilization at which you want to scale your app.
313
+
Before running the following command, replace the `<PLACEHOLDERS>` with your values.
311
314
312
315
# [Bash](#tab/bash)
313
316
@@ -339,9 +342,14 @@ az containerapp update `
339
342
340
343
### Memory scaling
341
344
342
-
Memory scaling allows your app to scale in or out depending on how much memory is being used. Memory scaling doesn't allow your container app to scale to 0. For more information about this trigger, see [KEDA memory scale trigger](https://keda.sh/docs/scalers/memory/).
345
+
Memory scaling allows your app to scale in or out depending on how much memory is being used. Memory scaling doesn't allow your container app to scale to zero. For more information about this trigger, see [KEDA memory scale trigger](https://keda.sh/docs/scalers/memory/).
346
+
347
+
Add a memory scale rule to your container app by running the `az containerapp update` command.
348
+
349
+
> [!NOTE]
350
+
> When you use the Azure CLI to add a scale rule to a container app that already has a scale rule, the new scale rule replaces the old scale rule. To see how to add multiple scale rules, see [Multiple scale rules](#multiple-scale-rules).
343
351
344
-
Add a memory scale rule to your container app by running the `az containerapp update`command. Replace the `<PLACEHOLDERS>` with your values. The memory utilization value is the percentage of memory utilization at which you want to scale your app.
352
+
Before running the following command, replace the `<PLACEHOLDERS>` with your values. The memory utilization value is the percentage of memory utilization at which you want to scale your app.
0 commit comments