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/azure-functions/container-concepts.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Describes the options for and benefits of running your function cod
4
4
ms.service: azure-functions
5
5
ms.custom: build-2024, linux-related-content
6
6
ms.topic: concept-article
7
-
ms.date: 04/05/2024
7
+
ms.date: 10/13/2024
8
8
9
9
#CustomerIntent: As a developer, I want to understand the options that are available to me for hosting function apps in Linux containers so I can choose the best development and deployment options for containerized deployments of function code to Azure.
10
10
---
@@ -23,7 +23,7 @@ There are several options for hosting your containerized function apps in Azure:
23
23
24
24
| Hosting option | Benefits |
25
25
| --- | --- |
26
-
|**[Azure Container Apps]**| Azure Functions provides integrated support for developing, deploying, and managing containerized function apps on [Azure Container Apps](../container-apps/overview.md). Use Azure Container Apps to host your function app containers when you need to run your event-driven functions in Azure in the same environment as other microservices, APIs, websites, workflows, or any container hosted programs. Container Apps hosting lets you run your functions in a managed Kubernetes-based environment with built-in support for open-source monitoring, mTLS, Dapr, and KEDA. Container Apps uses the power of the underlying Azure Kubernetes Service (AKS) while removing the complexity of having to work with Kubernetes APIs.<br/><br/>When youuse Container Apps integration, you can deploy, view, and manage your apps much like apps in a Functions-hosted container. You can also host a containerized function app directly in Container Apps without this integration.|
26
+
|**[Azure Container Apps]**| Azure Functions provides integrated support for developing, deploying, and managing containerized function apps on [Azure Container Apps](../container-apps/overview.md). This enables you to manage your apps using the same Functions tools and pages in the Azure portal. Use Azure Container Apps to host your function app containers when you need to run your event-driven functions in Azure in the same environment as other microservices, APIs, websites, workflows, or any container hosted programs. Container Apps hosting lets you run your functions in a managed Kubernetes-based environment with built-in support for open-source monitoring, mTLS, Dapr, and KEDA. Supports scale-to-zero and provides a servless pay-for-what-you-use hosting model. You can also request dedicated hardware, even GPUs, by using workload profiles. _Recommended hosting option for running containerized function apps on Azure._|
27
27
|**Azure Arc-enabled Kubernetes clusters (preview)**| You can host your function apps on Azure Arc-enabled Kubernetes clusters as either a [code-only deployment](./create-first-function-arc-cli.md) or in a [custom Linux container](./create-first-function-arc-custom-container.md). Azure Arc lets you attach Kubernetes clusters so that you can manage and configure them in Azure. _Hosting Azure Functions containers on Azure Arc-enabled Kubernetes clusters is currently in preview._|
28
28
|**[Azure Functions]**| You can host your containerized function apps in Azure Functions by running the container in either an [Elastic Premium plan](./functions-premium-plan.md) or a [Dedicated plan](./dedicated-plan.md). Premium plan hosting provides you with the benefits of dynamic scaling. You might want to use Dedicated plan hosting to take advantage of existing unused App Service plan resources. |
29
29
|**[Kubernetes]**| Because the Azure Functions runtime provides flexibility in hosting where and how you want, you can host and manage your function app containers directly in Kubernetes clusters. [KEDA](https://keda.sh) (Kubernetes-based Event Driven Autoscaling) pairs seamlessly with the Azure Functions runtime and tooling to provide event driven scale in Kubernetes. Just keep in mind that running your containerized function apps on Kubernetes, either by using KEDA or by direct deployment, is an open-source effort that you can use free of cost, with best-effort support provided by contributors and from the community. You're responsible for maintaining your own function app containers in a cluster, even when deploying to Azure Kubernetes Service (AKS). |
@@ -43,7 +43,7 @@ The degree to which various features and behaviors of Azure Functions are suppor
43
43
|[Core Tools deployment](./functions-run-local.md#deploy-containers)|[`func azurecontainerapps`](./functions-core-tools-reference.md#func-azurecontainerapps-deploy)| No | No | No |[`func kubernetes`](./functions-core-tools-reference.md#func-kubernetes-deploy)|
44
44
|[Revisions](../container-apps/revisions.md)| No | Yes |No |No |No |
|[App Service authentication](../app-service/overview-authentication-authorization.md)| Not currently available<sup>4</sup> | Yes | Yes | Yes | No |
@@ -57,12 +57,13 @@ The degree to which various features and behaviors of Azure Functions are suppor
57
57
|[Configurable memory/CPU count](../container-apps/workload-profiles-overview.md)| Yes | Yes | No | No | Yes |
58
58
| "Free grant" option |[Yes](../container-apps/billing.md#consumption-plan)|[Yes](../container-apps/billing.md#consumption-plan)| No | No | No |
59
59
| Pricing details |[Container Apps billing](../container-apps/billing.md)|[Container Apps billing](../container-apps/billing.md)|[Premium plan billing](./functions-premium-plan.md#billing)|[Dedicated plan billing](./dedicated-plan.md#billing)|[AKS pricing](/azure/aks/free-standard-pricing-tiers)|
60
+
| Service name requirements | 2-32 characters: limited to lowercase letters, numbers, and hyphens. Must start with a letter and end with an alphanumeric character. | 2-32 characters: limited to lowercase letters, numbers, and hyphens. Must start with a letter and end with an alphanumeric character. | Less than 64 characters: limited to alphanumeric characters and hyphens. Can't start with or end in a hyphen. | Less than 64 characters: limited to alphanumeric characters and hyphens. Can't start with or end in a hyphen. | Less than 253 characters: limited to alphanumeric characters and hyphens. Must start and end with an alphanumeric character. |
60
61
61
62
1. On Container Apps, the default is 10 instances, but you can set the [maximum number of replicas](../container-apps/scale-app.md#scale-definition), which has an overall maximum of 1000. This setting is honored as long as there's enough cores quota available. When you create your function app from the Azure portal, you're limited to 300 instances.
62
63
2. In some regions, Linux apps on a Premium plan can scale to 100 instances. For more information, see the [Premium plan article](functions-premium-plan.md#region-max-scale-out). <br/>
63
64
3. For specific limits for the various App Service plan options, see the [App Service plan limits](../azure-resource-manager/management/azure-subscription-service-limits.md#app-service-limits).
64
65
4. Feature parity is a goal of integrated hosting on Azure Container Apps.
65
-
5. Requires [KEDA](./functions-kubernetes-keda.md). Currently supported for these trigger types: Event Hubs, Queue storage, Kafka, Service Bus, Timer, and HTTP. Not currently supported for Blob storage, Event Grid, Durable, Redis, and Cosmos DB triggers.
66
+
5. Requires [KEDA](./functions-kubernetes-keda.md); supported by most triggers. To learn which triggers support event-driven scaling, see [Considerations for Container Apps hosting](functions-container-apps-hosting.md#considerations-for-container-apps-hosting).
66
67
6. When the [minimum number of replicas](../container-apps/scale-app.md#scale-definition) is set to zero, the default timeout depends on the specific triggers used in the app.
67
68
7. There's no maximum execution timeout duration enforced. However, the grace period given to a function execution is 60 minutes [during scale in](event-driven-scaling.md#scale-in-behaviors), and a grace period of 10 minutes is given during platform updates.
68
69
8. Requires the App Service plan be set to [Always On](dedicated-plan.md#always-on). A grace period of 10 minutes is given during platform updates.
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-container-apps-hosting.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Azure Container Apps hosting of Azure Functions
3
3
description: Learn about how you can use Azure Functions on Azure Container Apps to host and manage containerized function apps in Azure.
4
-
ms.date: 07/04/2024
4
+
ms.date: 10/18/2024
5
5
ms.topic: conceptual
6
6
ms.custom: build-2024, linux-related-content
7
7
# Customer intent: As a cloud developer, I want to learn more about hosting my function apps in Linux containers managed by Azure Container Apps.
@@ -91,10 +91,13 @@ If you run into any issues with these managed resource groups, you should contac
91
91
Keep in mind the following considerations when deploying your function app containers to Container Apps:
92
92
93
93
+ While all triggers can be used, only the following triggers can dynamically scale (from zero instances) when running in a Container Apps environment:
0 commit comments