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/app-service/overview-arc-integration.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,7 +104,7 @@ No. Apps cannot be assigned managed identities when running in Azure Arc. If you
104
104
105
105
### Are there any scaling limits?
106
106
107
-
All applications deployed with Azure App Service on Kubernetes with Azure Arc are able to scale within the limits of the underlying Kubernetes cluster. If the underlying Kubernetes Cluster runs out of available compute resources (CPU and memory primarily), then applications will only be able to scale to the number of instances of the application that Kubernetes can schedule with available resource.
107
+
All applications deployed with Azure App Service on Kubernetes with Azure Arc are able to scale within the limits of the underlying Kubernetes cluster. If the underlying Kubernetes Cluster runs out of available compute resources (CPU and memory primarily), then applications will only be able to scale to the number of instances of the application that Kubernetes can schedule with available resource.
108
108
109
109
### What logs are collected?
110
110
@@ -136,7 +136,7 @@ ARM64 based clusters are not supported at this time.
136
136
- Upgrade Azure Function runtime to v3.3.1
137
137
- Set default replica count of App Controller and Envoy Controller to 2 to add further stability
138
138
139
-
If your extension was in the stable version and auto-upgrade-minor-version is set to true, the extension upgrades automatically. To manually upgrade the extension to the latest version, you can run the command:
139
+
If your extension was in the stable version and auto-upgrade-minor-version is set to true, the extension upgrades automatically. To manually upgrade the extension to the latest version, you can run the command:
@@ -150,7 +150,7 @@ If your extension was in the stable version and auto-upgrade-minor-version is se
150
150
- Resolved issues that caused slot swap operations to fail
151
151
- Resolved issues customers experienced during creation of Ruby web applications
152
152
153
-
If your extension was in the stable version and auto-upgrade-minor-version is set to true, the extension upgrades automatically. To manually upgrade the extension to the latest version, you can run the command:
153
+
If your extension was in the stable version and auto-upgrade-minor-version is set to true, the extension upgrades automatically. To manually upgrade the extension to the latest version, you can run the command:
@@ -160,7 +160,7 @@ If your extension was in the stable version and auto-upgrade-minor-version is se
160
160
161
161
- Minor release to resolve issue with CRD update
162
162
163
-
If your extension was in the stable version and auto-upgrade-minor-version is set to true, the extension upgrades automatically. To manually upgrade the extension to the latest version, you can run the command:
163
+
If your extension was in the stable version and auto-upgrade-minor-version is set to true, the extension upgrades automatically. To manually upgrade the extension to the latest version, you can run the command:
@@ -173,7 +173,7 @@ If your extension was in the stable version and auto-upgrade-minor-version is se
173
173
- Upgrade Envoy to 1.20.1
174
174
- Resolved issue with Application Insights support for .NET Applications
175
175
176
-
If your extension was in the stable version and auto-upgrade-minor-version is set to true, the extension upgrades automatically. To manually upgrade the extension to the latest version, you can run the command:
176
+
If your extension was in the stable version and auto-upgrade-minor-version is set to true, the extension upgrades automatically. To manually upgrade the extension to the latest version, you can run the command:
0 commit comments