Merge pull request #299280 from craigshoemaker/aca/release-build-container-apps

Stacyrch140 · web-flow · commit 0077951bf3de · 2025-05-02T19:39:28.000-04:00
[Container Apps] Remove preview labels for features going GA
diff --git a/articles/container-apps/aspire-dashboard.md b/articles/container-apps/aspire-dashboard.md
@@ -6,12 +6,12 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli, devx-track-dotnet
 ms.topic: how-to
-ms.date: 1/14/2025
+ms.date: 05/02/2025
 ms.author: cshoe
 zone_pivot_groups: azure-azd-cli-portal
 ---
 
-# Read real time app data with Aspire Dashboard in Azure Container Apps (preview)
+# Read real time app data with Aspire Dashboard in Azure Container Apps
 
 The [Aspire Dashboard](/dotnet/aspire/fundamentals/dashboard/overview) displays live data about how applications and other resources are running within an environment.
 
diff --git a/articles/container-apps/azure-arc-create-container-app.md b/articles/container-apps/azure-arc-create-container-app.md
@@ -6,13 +6,13 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: conceptual
-ms.date: 02/03/2025
+ms.date: 05/02/2025
 ms.author: cshoe
 ---
 
-# Tutorial: Create an Azure Container App on Azure Arc-enabled Kubernetes (Preview)
+# Tutorial: Create an Azure Container App on Azure Arc-enabled Kubernetes
 
-In this tutorial, you create a [Container app to an Azure Arc-enabled Kubernetes cluster](azure-arc-enable-cluster.md) (Preview) and learn to:
+In this tutorial, you create a [Container app to an Azure Arc-enabled Kubernetes cluster](azure-arc-enable-cluster.md) and learn to:
 
 > [!div class="checklist"]
 > * Create a container app on Azure Arc
diff --git a/articles/container-apps/azure-arc-enable-cluster.md b/articles/container-apps/azure-arc-enable-cluster.md
@@ -6,11 +6,11 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: tutorial
-ms.date: 02/03/2025
+ms.date: 05/02/2025
 ms.author: cshoe
 ---
 
-# Tutorial: Enable Azure Container Apps on Azure Arc-enabled Kubernetes (Preview)
+# Tutorial: Enable Azure Container Apps on Azure Arc-enabled Kubernetes
 
 With [Azure Arc-enabled Kubernetes clusters](/azure/azure-arc/kubernetes/overview), you can create a [Container Apps enabled custom location](azure-arc-create-container-app.md) in your on-premises or cloud Kubernetes cluster to deploy your Azure Container Apps applications as you would any other region.
 
diff --git a/articles/container-apps/azure-arc-overview.md b/articles/container-apps/azure-arc-overview.md
@@ -5,11 +5,11 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 03/06/2025
+ms.date: 05/02/2025
 ms.author: cshoe
 ---
 
-# Azure Container Apps on Azure Arc (Preview)
+# Azure Container Apps on Azure Arc
 
 You can run Container Apps on an Azure Arc-enabled AKS or AKS on Azure Local cluster.
 
@@ -36,7 +36,7 @@ The following public preview limitations apply to Azure Container Apps on Azure
 
 | Limitation | Details |
 |---|---|
-| Supported Azure regions | East US, West Europe, East Asia |
+| Supported Azure regions | Central US, East Asia, East US, North Central US, Southeast Asia, Sweden Central, UK South, West Europe, West US |
 | Cluster networking requirement | Must support [LoadBalancer](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer) service type |
 | Node OS requirement | **Linux** only. | 
 | Feature: Managed identities | [Not available](#are-managed-identities-supported) |
@@ -73,7 +73,7 @@ The following table describes the role of each revision created for you:
 | dapr-placement-server | Used for Actors only - creates mapping tables that map actor instances to pods | 1 | 100 millicpu | 500 MB | StatefulSet |
 | dapr-sentry | Manages mTLS between services and acts as a CA | 2 | 800 millicpu | 200 MB | ReplicaSet |
 
-## FAQ for Azure Container Apps on Azure Arc (Preview)
+## FAQ for Azure Container Apps on Azure Arc
 
 - [How much does it cost?](#how-much-does-it-cost)
 - [Which Container Apps features are supported?](#which-container-apps-features-are-supported)
diff --git a/articles/container-apps/container-apps-extension-release-notes.md b/articles/container-apps/container-apps-extension-release-notes.md
@@ -97,6 +97,7 @@ ms.author: cshoe
 - Allow customers to enabled Azure SDK debug logging in Dapr
 - Scale Envoy in response to memory usage
 - Change of Envoy log format to JSON
+- Export additional Envoy metrics
 - Export more Envoy metrics
 - Truncate Envoy log to first 1,024 characters when log content failed to parse
 - Handle SIGTERM gracefully in local proxy
diff --git a/articles/container-apps/how-to-integrate-with-azure-front-door.md b/articles/container-apps/how-to-integrate-with-azure-front-door.md
@@ -6,12 +6,12 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, ignite-2024
 ms.topic:  how-to
-ms.date: 03/31/2025
+ms.date: 05/02/2025
 ms.author: cshoe
 zone_pivot_groups: azure-cli-or-portal
 ---
 
-# Create a private link to an Azure Container App with Azure Front Door (preview)
+# Create a private link to an Azure Container App with Azure Front Door
 
 In this article, you learn how to connect directly from Azure Front Door to your Azure Container Apps using a private link instead of the public internet. In this tutorial, you create an Azure Container Apps workload profiles environment, an Azure Front Door, and connect them securely through a private link. You then verify the connectivity between your container app and the Azure Front Door.
 
diff --git a/articles/container-apps/how-to-use-private-endpoint.md b/articles/container-apps/how-to-use-private-endpoint.md
@@ -1,24 +1,22 @@
 ---
-title: Use a private endpoint with an Azure Container Apps environment (preview)
+title: Use a private endpoint with an Azure Container Apps environment
 description: Learn how to use a private endpoint with an Azure Container Apps environment.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, ignite-2024
 ms.topic:  how-to
-ms.date: 02/03/2025
+ms.date: 05/02/2025
 ms.author: cshoe
 zone_pivot_groups: azure-cli-or-portal
 ---
 
-# Use a private endpoint with an Azure Container Apps environment (preview)
+# Use a private endpoint with an Azure Container Apps environment
 
 In this article, you learn how to use a private endpoint to securely access your Azure Container App without exposing it to the public Internet.
 
 A private endpoint uses a private IP address from your virtual network (VNet). This endpoint connects you privately and securely to a service powered by [Azure Private Link](/azure/private-link/private-link-overview).
 
-Private endpoints on Azure Container Apps only support inbound HTTP traffic. TCP traffic isn't supported.
-
 ::: zone pivot="azure-portal"
 
 ## Prerequisites
diff --git a/articles/container-apps/ingress-overview.md b/articles/container-apps/ingress-overview.md
@@ -7,7 +7,7 @@ ms.service: azure-container-apps
 ms.custom:
   - ignite-2024
 ms.topic: conceptual
-ms.date: 05/03/2023
+ms.date: 05/02/2025
 ms.author: cshoe
 ---
 
@@ -55,7 +55,7 @@ With HTTP ingress enabled, your container app has:
 - Endpoints that expose ports 80 (for HTTP) and 443 (for HTTPS)
   - By default, HTTP requests to port 80 are automatically redirected to HTTPS on 443
 - A fully qualified domain name (FQDN)
-- Request timeout is 240 seconds
+- Request time out is 240 seconds
 
 #### HTTP headers
 
@@ -64,7 +64,7 @@ HTTP ingress adds headers to pass metadata about the client request to your cont
 | Header | Description | Values |
 |---|---|---|
 | `X-Forwarded-Proto` | Protocol used by the client to connect with the Container Apps service. | `http` or `https` |
-| `X-Forwarded-For` | The IP address of the client that sent the request. | IP address of the sender. If specified in intital request, it will be overwritten. |
+| `X-Forwarded-For` | The IP address of the client that sent the request. | IP address of the sender. If specified in initial request, it is overwritten. |
 | `X-Forwarded-Host` | The host name the client used to connect with the Container Apps service. |  |
 | `X-Forwarded-Client-Cert` | The client certificate if `clientCertificateMode` is set. | Semicolon separated list of Hash, Cert, and Chain. For example: `Hash=....;Cert="...";Chain="...";` |
 
@@ -73,7 +73,7 @@ HTTP ingress adds headers to pass metadata about the client request to your cont
 Container Apps supports TCP-based protocols other than HTTP or HTTPS. For example, you can use TCP ingress to expose a container app that uses the [Redis protocol](https://redis.io/topics/protocol).
 
 > [!NOTE]
-> External TCP ingress is only supported for Container Apps environments that use a [custom VNET](vnet-custom.md). TCP ingress is not supported for apps that accept inbound traffic through a [private endpoint](networking.md#private-endpoint).
+> External TCP ingress is only supported for Container Apps environments that use a [custom VNET](vnet-custom.md).
 
 With TCP ingress enabled, your container app:
 
@@ -88,14 +88,22 @@ In addition to the main HTTP/TCP port for your container apps, you might expose
 > To use this feature, you must have the container apps CLI extension. Run `az extension add -n containerapp` in order to install the latest version of the container apps CLI extension.
 
 The following apply to additional TCP ports:
-- Additional TCP ports can only be external if the app itself is set as external and the container app is using a custom VNet.
-- Any externally exposed additional TCP ports must be unique across the entire Container Apps environment. This includes all external additional TCP ports, external main TCP ports, and 80/443 ports used by built-in HTTP ingress. If the additional ports are internal, the same port can be shared by multiple apps.
-- If an exposed port isn't provided, the exposed port will default to match the target port.
+
+- More TCP ports can only be external if the app itself is set as external and the container app is using a custom VNet.
+
+- Any externally exposed extra TCP ports must be unique across the entire Container Apps environment. This includes all external extra TCP ports, external main TCP ports, and 80/443 ports used by built-in HTTP ingress. If the extra ports are internal, you can share the same port by multiple apps.
+
+- If an exposed port isn't provided, the exposed port defaults to match the target port.
+
 - Each target port must be unique, and the same target port can't be exposed on different exposed ports.
-- There's a maximum of five additional ports per app. If additional ports are required, please open a support request.
-- Only the main ingress port supports built-in HTTP features such as CORS and session affinity. When running HTTP on top of the additional TCP ports, these built-in features aren't supported.
 
-Visit the [how to article on ingress](ingress-how-to.md#use-additional-tcp-ports) for more information on how to enable additional ports for your container apps.
+- There's a maximum of five additional ports per app. If additional ports are required, open a support request.
+
+- Only the main ingress port supports built-in HTTP features such as CORS and session affinity. When running HTTP on top of the extra TCP ports, these built-in features aren't supported.
+
+- Port number `36985` is a reserved for internal health checks and isn't available to TCP applications or extra exposed ports on HTTP applications.
+
+For more information on how to enable extra ports, see [Configure ingress for your app](ingress-how-to.md#use-additional-tcp-ports).
 
 ## Domain names
 
@@ -125,7 +133,7 @@ Containers Apps allows you to split incoming traffic between active revisions. W
 
 ## Session affinity
 
-Session affinity, also known as sticky sessions, is a feature that allows you to route all HTTP requests from a client to the same container app replica. This feature is useful for stateful applications that require a consistent connection to the same replica.  For more information, see [Session affinity](sticky-sessions.md).
+Session affinity, also known as sticky sessions, is a feature that allows you to route all HTTP requests from a client to the same container app replica. This feature is useful for stateful applications that require a consistent connection to the same replica. For more information, see [Session affinity](sticky-sessions.md).
 
 ## Cross origin resource sharing (CORS)
 
diff --git a/articles/container-apps/networking.md b/articles/container-apps/networking.md
@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic:  conceptual
-ms.date: 03/20/2025
+ms.date: 05/02/2025
 ms.author: cshoe
 ---
 
@@ -310,7 +310,7 @@ In order to connect to your container apps through a private endpoint, you must
 ### Environment security
 
 > [!NOTE]
-> To control ingress traffic, you can also [use private endpoints with a private connection to Azure Front Door](how-to-integrate-with-azure-front-door.md) in place of Application Gateway. This feature is in preview.
+> To control ingress traffic, you can also [use private endpoints with a private connection to Azure Front Door](how-to-integrate-with-azure-front-door.md) in place of Application Gateway.
 
 :::image type="content" source="media/networking/locked-down-network.png" alt-text="Diagram of how to fully lock down your network for Container Apps.":::
 
diff --git a/articles/container-apps/opentelemetry-agents.md b/articles/container-apps/opentelemetry-agents.md
@@ -1,10 +1,10 @@
 ---
-title: Collect and read OpenTelemetry data in Azure Container Apps (preview)
-description: Learn to record and query data collected using OpenTelemetry in Azure Container Apps.
+title: Collect and read OpenTelemetry data in Azure Container Apps
+description: Learn to record and query data collected using OpenTelemetry in Azure Container Apps (preview).
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
-ms.date: 04/28/2025
+ms.date: 05/02/2025
 ms.author: cshoe
 ms.topic: how-to
 ---
@@ -48,7 +48,7 @@ The following table shows you what type of data you can send to each destination
 | Destination | Logs | Metrics | Traces |
 |---|------|---------|--------|
 | [Azure App Insights](/azure/azure-monitor/app/app-insights-overview) | Yes | No | Yes |
-| [Datadog](https://datadoghq.com/) | No | Yes | Yes |
+| [Datadog](https://datadoghq.com/) | Yes | Yes | Yes |
 | [OpenTelemetry](https://opentelemetry.io/) protocol (OTLP) configured endpoint | Yes | Yes | Yes |
 
 ## Azure Monitor Application Insights
@@ -771,7 +771,6 @@ See the destination service for their billing structure and terms. For example,
 
 ## Known limitations
 
-- OpenTelemetry agents are in preview.
 - System data, such as system logs or Container Apps standard metrics, isn't available to be sent to the OpenTelemetry agent.
 - The Application Insights endpoint doesn't accept metrics.
 - The Datadog endpoint doesn't accept logs.
diff --git a/articles/container-apps/planned-maintenance.md b/articles/container-apps/planned-maintenance.md
@@ -1,17 +1,17 @@
 ---
-title: Azure Container Apps planned maintenance (preview)
+title: Azure Container Apps planned maintenance
 description: Configure system-level planned maintenance in Azure Container Apps
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom:
   - ignite-2024
 ms.topic: how-to
-ms.date: 12/05/2024
+ms.date: 05/02/2025
 ms.author: cshoe
 ---
 
-# Azure Container Apps planned maintenance (preview)
+# Azure Container Apps planned maintenance
 
 Azure Container Apps is a fully managed service where platform and infrastructure updates are regularly and automatically applied to both components and environments. The Container Apps update system is designed to minimize the effect on performance of your apps during updates. By defining maintenance windows, you can designate the most advantageous times for your application.
 
@@ -24,6 +24,10 @@ The following table describes the difference between the timing in how *critical
 | Critical | Urgent fixes that include updates essential to the security and stability of your app. | Anytime |
 | Noncritical | Routine security patches, bug fixes, and the introduction of new features. | If a planned maintenance window is defined, then updates only start during that time span.<br><br>If a maintenance window isn't configured, then updates can be applied at any time. |
 
+Planned maintenance capabilities are available via the Azure portal and Azure CLI.
+
+To change your planned maintenance settings in the portal, open your Container Apps environment. From the side menu, open *Settings* and then select **Planned Maintenance**.
+
 ## How maintenance windows work
 
 To control the timing for noncritical updates, you can define a weekly time range for when updates are applied to your environment. When you define a maintenance window, you specify a day of the week, a start time in the UTC format, and a duration.
@@ -118,10 +122,6 @@ In the *Diagnose and solve problems* window, you can view the configured mainten
 
 :::image type="content" source="media/planned-maintenance/azure-container-apps-planned-maintenance-upgrade-events.png" alt-text="Screenshot of an Azure Container Apps planned maintenance event history graph." lightbox="media/planned-maintenance/azure-container-apps-planned-maintenance-upgrade-events.png":::
 
-## Considerations
-
-Planned maintenance is free during preview.
-
 ## Next steps
 
 > [!div class="nextstepaction"]
diff --git a/articles/container-apps/sessions-tutorial-nodejs.md b/articles/container-apps/sessions-tutorial-nodejs.md
@@ -20,9 +20,6 @@ In this tutorial you:
 > * Set the appropriate security context for your session pool
 > * Pass in JavaScript code for the container app to run
 
-> [!NOTE]
-> The JavaScript code interpreter feature in Azure Container Apps dynamic sessions is currently in preview. For more information, see [preview limitations](./sessions.md#region-availability).
-
 ## Prerequisites
 
 You need the following resources before you begin this tutorial.
diff --git a/articles/container-apps/workload-profiles-overview.md b/articles/container-apps/workload-profiles-overview.md
@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 11/05/2024
+ms.date: 05/02/2024
 ms.author: cshoe
 ms.custom:
   - references_regions
@@ -25,7 +25,7 @@ Profiles are configured to fit the different needs of your applications.
 | Consumption GPU | Scale-to-zero serverless GPUs are available in West US 3, Australia East, and Sweden Central regions. | Apps that require GPU |
 | Dedicated (General purpose) | Balance of memory and compute resources | Apps that require larger amounts of CPU and/or memory |
 | Dedicated (Memory optimized) | Increased memory resources | Apps that need access to large in-memory data, in-memory machine learning models, or other high memory requirements |
-| Dedicated (GPU enabled) (preview) | GPU enabled with increased memory and compute resources available in West US 3 and North Europe regions. | Apps that require GPU |
+| Dedicated (GPU enabled) | GPU enabled with increased memory and compute resources available in West US 3 and North Europe regions. | Apps that require GPU |
 
 > [!NOTE]
 > When using GPU-enabled workload profiles, make sure your application is running the latest version of [CUDA](https://catalog.ngc.nvidia.com/orgs/nvidia/containers/cuda).
@@ -65,9 +65,9 @@ There are different types and sizes of workload profiles available by region. By
 | Dedicated-E8 | E8 | 8 | 64 | - | Memory optimized | per node | Managed Environment Memory Optimized Cores |
 | Dedicated-E16 | E16 | 16 | 128 | - | Memory optimized | per node | Managed Environment Memory Optimized Cores |
 | Dedicated-E32 | E32 | 32 | 256 | - | Memory optimized | per node | Managed Environment Memory Optimized Cores |
-| Dedicated-NC24-A100 (preview) | NC24-A100 | 24 | 220 | 1 | GPU enabled | per node<sup>\*</sup> | Subscription NCA 100 Gpus |
-| Dedicated-NC48-A100 (preview) | NC48-A100 | 48 | 440 | 2 | GPU enabled | per node<sup>\*</sup> | Subscription NCA 100 Gpus |
-| Dedicated-NC96-A100 (preview) | NC96-A100 | 96 | 880 | 4 | GPU enabled | per node<sup>\*</sup> | Subscription NCA 100 Gpus |
+| Dedicated-NC24-A100 | NC24-A100 | 24 | 220 | 1 | GPU enabled | per node<sup>\*</sup> | Subscription NCA 100 Gpus |
+| Dedicated-NC48-A100 | NC48-A100 | 48 | 440 | 2 | GPU enabled | per node<sup>\*</sup> | Subscription NCA 100 Gpus |
+| Dedicated-NC96-A100 | NC96-A100 | 96 | 880 | 4 | GPU enabled | per node<sup>\*</sup> | Subscription NCA 100 Gpus |
 
 <sup>\*</sup> Capacity is allocated on a per-case basis. Submit a [support ticket](https://azure.microsoft.com/support/create-ticket/) to request the capacity amount required for your application.
 
