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
Copy file name to clipboardExpand all lines: articles/container-apps/scale-app.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,8 @@ Azure Container Apps manages automatic horizontal scaling through a set of decla
17
17
18
18
Adding or editing scaling rules creates a new revision of your container app. A revision is an immutable snapshot of your container app. See revision [change types](./revisions.md#change-types) to review which types of changes trigger a new revision.
19
19
20
+
[Event-driven Container Apps jobs](jobs.md#event-driven-jobs) use scaling rules to trigger executions based on events.
21
+
20
22
## Scale definition
21
23
22
24
Scaling is defined by the combination of limits, rules, and behavior.
@@ -60,7 +62,7 @@ If you define more than one scale rule, the container app begins to scale once t
60
62
61
63
## HTTP
62
64
63
-
With an HTTP scaling rule, you have control over the threshold of concurrent HTTP requests that determines how your container app revision scales.
65
+
With an HTTP scaling rule, you have control over the threshold of concurrent HTTP requests that determines how your container app revision scales.[Container Apps jobs](jobs.md) don't support HTTP scaling rules.
64
66
65
67
In the following example, the revision scales out up to five replicas and can scale in to zero. The scaling property is set to 100 concurrent requests per second.
66
68
@@ -155,7 +157,7 @@ az containerapp create \
155
157
156
158
## TCP
157
159
158
-
With a TCP scaling rule, you have control over the threshold of concurrent TCP connections that determines how your app scales.
160
+
With a TCP scaling rule, you have control over the threshold of concurrent TCP connections that determines how your app scales.[Container Apps jobs](jobs.md) don't support TCP scaling rules.
159
161
160
162
In the following example, the container app revision scales out up to five replicas and can scale in to zero. The scaling threshold is set to 100 concurrent connections per second.
161
163
@@ -236,6 +238,8 @@ You can create a custom Container Apps scaling rule based on any [ScaledObject](
236
238
| Polling interval | 30 |
237
239
| Cool down period | 300 |
238
240
241
+
For [event-driven Container Apps jobs](jobs.md#event-driven-jobs), you can create a custom scaling rule based on any [ScaledJob](https://keda.sh/docs/latest/concepts/scaling-jobs/)-based KEDA scalers.
242
+
239
243
The following example demonstrates how to create a custom scale rule.
240
244
241
245
### Example
@@ -386,13 +390,13 @@ A KEDA scaler may support using secrets in a [TriggerAuthentication](https://ked
0 commit comments