Skip to content

Commit f6680bd

Browse files
Merge pull request #257915 from anthonychu/patch-22
[Container Apps] Update scaling doc for jobs
2 parents 34825ee + 34e573e commit f6680bd

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

articles/container-apps/scale-app.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ Azure Container Apps manages automatic horizontal scaling through a set of decla
1717

1818
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.
1919

20+
[Event-driven Container Apps jobs](jobs.md#event-driven-jobs) use scaling rules to trigger executions based on events.
21+
2022
## Scale definition
2123

2224
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
6062

6163
## HTTP
6264

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.
6466

6567
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.
6668

@@ -155,7 +157,7 @@ az containerapp create \
155157

156158
## TCP
157159

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.
159161

160162
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.
161163

@@ -236,6 +238,8 @@ You can create a custom Container Apps scaling rule based on any [ScaledObject](
236238
| Polling interval | 30 |
237239
| Cool down period | 300 |
238240

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+
239243
The following example demonstrates how to create a custom scale rule.
240244

241245
### Example
@@ -386,13 +390,13 @@ A KEDA scaler may support using secrets in a [TriggerAuthentication](https://ked
386390

387391
::: zone pivot="azure-portal"
388392

389-
1. Go to your container app in the Azure portal
393+
1. Go to your container app in the Azure portal.
390394

391395
1. Select **Scale**.
392396

393397
1. Select **Edit and deploy**.
394398

395-
1. Select the **Scale** tab.
399+
1. Select the **Scale and replicas** tab.
396400

397401
1. Select the minimum and maximum replica range.
398402

0 commit comments

Comments
 (0)