Skip to content

Commit 3539bae

Browse files
Merge pull request #258696 from ggailey777/patch-2
[Functions] ACA hosting clarifications and updates
2 parents 052300a + 7755b26 commit 3539bae

File tree

2 files changed

+5
-6
lines changed

2 files changed

+5
-6
lines changed

articles/azure-functions/functions-container-apps-hosting.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Azure Container Apps hosting of Azure Functions
33
description: Learn about how you can use Azure Container Apps to host containerized function apps in Azure Functions.
4-
ms.date: 07/30/2023
4+
ms.date: 11/15/2023
55
ms.topic: conceptual
66
ms.custom: references_regions, build-2023
77
# Customer intent: As a cloud developer, I want to learn more about hosting my function apps in Linux containers by using Azure Container Apps.
@@ -73,12 +73,10 @@ Keep in mind the following considerations when deploying your function app conta
7373
+ Azure Event Hubs
7474
+ Kafka*
7575
\*The protocol value of `ssl` isn't supported when hosted on Container Apps. Use a [different protocol value](functions-bindings-kafka-trigger.md?pivots=programming-language-csharp#attributes).
76-
+ Dapr is currently enabled by default in the preview release. In a later release, Dapr loading should be configurable.
7776
+ For the built-in Container Apps [policy definitions](../container-apps/policy-reference.md#policy-definitions), currently only environment-level policies apply to Azure Functions containers.
7877
+ When using Container Apps, you don't have direct access to the lower-level Kubernetes APIs.
79-
+ Use of user-assigned managed identities is currently supported, and is preferred for accessing Azure Container Registry. For more information, see [Add a user-assigned identity](../app-service/overview-managed-identity.md?toc=%2Fazure%2Fazure-functions%2Ftoc.json#add-a-user-assigned-identity).
8078
+ The `containerapp` extension conflicts with the `appservice-kube` extension in Azure CLI. If you have previously published apps to Azure Arc, run `az extension list` and make sure that `appservice-kube` isn't installed. If it is, you can remove it by running `az extension remove -n appservice-kube`.
81-
+ To invoke DAPR APIs or to run the [Functions Dapr extension](https://github.com/Azure/azure-functions-dapr-extension), make sure the minimum replica count is set to at least `1`. This enables the DAPR sidecar to run in the background to handle DAPR requests. The Functions Dapr extension is also in preview, with help provided [in the repository](https://github.com/Azure/azure-functions-dapr-extension/issues).
79+
+ The Functions Dapr extension is also in preview, with help provided [in the repository](https://github.com/Azure/azure-functions-dapr-extension/issues).
8280

8381
## Next steps
8482

includes/functions-create-container-registry.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: ggailey777
33
ms.service: azure-functions
44
ms.topic: include
5-
ms.date: 06/05/2023
5+
ms.date: 11/15/2023
66
ms.author: glenga
77
---
88

@@ -369,8 +369,9 @@ Azure Container Apps is a private registry service for building, storing, and ma
369369
az acr update -n <REGISTRY_NAME> --admin-enabled true
370370
```
371371
372+
<!---Hide until Functions + ACA supports managed identities
372373
> [!IMPORTANT]
373-
> The admin account is designed for a single user to access the registry, mainly for testing purposes and for specific Azure services. In a production scenario, you should instead [add a user-assigned managed identity](../articles/app-service/overview-managed-identity.md?toc=%2Fazure%2Fazure-functions%2Ftoc.json&tabs=cli#add-a-user-assigned-identity) to which you can [grant access to the registry](../articles/container-registry/container-registry-authentication-managed-identity.md?tabs=azure-cli#grant-identity-access-to-the-container-registry).
374+
> The admin account is designed for a single user to access the registry, mainly for testing purposes and for specific Azure services. In a production scenario, you should instead [add a user-assigned managed identity](../articles/app-service/overview-managed-identity.md?toc=%2Fazure%2Fazure-functions%2Ftoc.json&tabs=cli#add-a-user-assigned-identity) to which you can [grant access to the registry](../articles/container-registry/container-registry-authentication-managed-identity.md?tabs=azure-cli#grant-identity-access-to-the-container-registry). -->
374375
375376
1. Use the following command to retrieve the admin username and password, which Functions needs to connect to the registry:
376377

0 commit comments

Comments
 (0)