Skip to content

Commit e1850db

Browse files
authored
Improvements to document quality
1 parent 0645bcf commit e1850db

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/container-apps/azure-arc-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ During the preview period, certain Azure Container App features are being valida
8989

9090
### Are managed identities supported?
9191

92-
No. Apps can't be assigned managed identities when running in Azure Arc. If your app needs an identity for working with another Azure resource, consider using an [application service principal](../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) instead.
92+
Managed Identities are not supported. Apps can't be assigned managed identities when running in Azure Arc. If your app needs an identity for working with another Azure resource, consider using an [application service principal](../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) instead.
9393

9494
### Are there any scaling limits?
9595

@@ -105,7 +105,7 @@ By default, logs from system components are sent to the Azure team. Application
105105

106106
### What do I do if I see a provider registration error?
107107

108-
As you create an Azure Container Apps connected environment resource, some subscriptions might see the "No registered resource provider found" error. The error details might include a set of locations and api versions that are considered valid. If this error message is returned, the subscription must be re-registered with the `Microsoft.App` provider. Re-registering the provider has no effect on existing applications or APIs. To re-register, use the Azure CLI to run `az provider register --namespace Microsoft.App --wait`. Then reattempt the connected environment command.
108+
As you create an Azure Container Apps connected environment resource, some subscriptions might see the "No registered resource provider found" error. The error details might include a set of locations and API versions that are considered valid. If this error message is returned, the subscription must be re-registered with the `Microsoft.App` provider. Re-registering the provider has no effect on existing applications or APIs. To re-register, use the Azure CLI to run `az provider register --namespace Microsoft.App --wait`. Then reattempt the connected environment command.
109109

110110
### Can I deploy the Container Apps extension on an ARM64 based cluster?
111111

@@ -210,8 +210,8 @@ ARM64 based clusters aren't supported at this time.
210210
- Scale Envoy in response to memory usage
211211
- Change of Envoy log format to Json
212212
- Export additional Envoy metrics
213+
- Truncate Envoy log to first 1024 characters when log content failed to parse
213214
- Handle SIGTERM gracefully in local proxy
214-
- Truncate Enoy log to first 1024 characters when log content failed to parse
215215
- Allow ability to leverage different namespaces with KEDA
216216
- Validation added for scale rule name
217217
- Enabled revision GC by default

0 commit comments

Comments
 (0)