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
- Elaborating that the mentioned pollingInterval and cooldownPeriod values also apply to the HTTP scaler. The HTTP scaler is a custom, non-Keda scaler, thus the suggested update.
- Added a link to the Keda ScaledObject documentation about pollingInterval and cooldownPeriod, so that readers can refer to the Keda documentation for further information about how these mechanisms work.
Copy file name to clipboardExpand all lines: articles/container-apps/scale-app.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ There are two scale properties that apply to all rules in your container app:
29
29
- Replicas not processing, but that remain in memory are billed in the "idle charge" category.
30
30
- Changes to scaling rules are a [revision-scope](revisions.md#revision-scope-changes) change.
31
31
- It's recommended to set the `properties.configuration.activeRevisionsMode` property of the container app to `single`, when using non-HTTP event scale rules.
32
-
- Container Apps implements the KEDA ScaledObject with the following default settings.
32
+
- Container Apps implements the KEDA [ScaledObject](https://keda.sh/docs/1.4/concepts/scaling-deployments/#details) and HTTP scaler with the following default settings.
0 commit comments