Merge pull request #2689 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-13 23:04 UTC

Author: learn-build-service-prod[bot]

articles/aks/azure-csi-driver-volume-provisioning.md

@@ -2970,6 +2970,7 @@ The Azure Files CSI driver also supports Windows nodes and containers. To use Wi
 [az-storage-account-create]: /cli/azure/storage/account#az-storage-account-create
 [az-storage-share-create]: /cli/azure/storage/share#az-storage-share-create
 [azure-container-storage]: /azure/storage/container-storage/container-storage-introduction
+[azure-datalake-storage-account]: /azure/storage/blobs/data-lake-storage-introduction
 [azure-disk-volume]: azure-disk-volume.md
 [azure-files-pvc]: azure-files-dynamic-pv.md
 [azure-files-usage]: /azure/storage/files/understand-performance#choosing-a-performance-tier-based-on-usage-patterns

articles/aks/best-practices-storage-nvme.md

@@ -165,10 +165,8 @@ There are several ways to use ephemeral NVMe data disks in your AKS workloads. T
 
 ### Azure Container Storage (recommended)
 
-
 [Azure Container Storage](/azure/storage/container-storage/container-storage-introduction) is a Kubernetes-native storage solution that abstracts and manages local NVMe disks as persistent volumes, with advanced orchestration and data services.
 
-
 You can deploy Azure Container Storage in your AKS cluster and provision volumes using standard Kubernetes PVCs.
 
 Azure Container Storage offers the following advantages:
@@ -178,37 +176,31 @@ Azure Container Storage offers the following advantages:
   - Improved reliability and operational simplicity.
   - Enables high-performance workloads with default volume striping cross all available disks.
 
-
-
 Azure Container Storage is the best option for Kubernetes workloads to orchestrate ephemeral NVMe data disks. It combines the raw performance of NVMe disks with Kubernetes-native management, security, and built-in integration with Azure’s monitoring features and Prometheus. This approach reduces operational complexity, improves reliability, and enables advanced scenarios (such as scaling and failover) that are difficult to achieve with `emptyDir` or `hostPath`.
 
 For more information, see [Azure Container Storage documentation](/azure/storage/container-storage/container-storage-introduction).
 
 ### `emptyDir` Volumes
 
+`[emptyDir](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir)` is a Kubernetes volume type that uses the node's local storage. By default, it uses the kubelet storage path on the OS disk, but you can configure it to use local NVMe disks for higher throughput and lower latency with temporary data.
 
-`emptyDir` is a Kubernetes volume type that uses the node's local storage. When backed by NVMe disks, `emptyDir` provides high throughput and low latency for temporary data.
-
-
-To use this method, define an `emptyDir` volume in your Pod spec. By default, it uses the fastest available storage (NVMe if present).
+To back `emptyDir` volumes with local NVMe disks, you must configure the kubelet storage path to point to an NVMe mount point during node initialization. This requires custom node bootstrap scripting and careful planning, as the configuration is immutable after node provisioning.
 
 #### Advantages
   - Simple to use and configure.
   - No external dependencies.
   - High performance when backed by NVMe.
 
 #### Disadvantages
-  - Data is lost if the Pod is rescheduled to another node.
+  - Data is deleted if the Pod is removed from the node.
   - No data persistence or replication.
   - Limited to single NVMe disk.
 
 ### `hostPath` Volumes
 
-
 `hostPath` mounts a specific directory or disk from the node’s filesystem into the Pod. You can target NVMe mount points directly.
 
-
-To use this method, specify the NVMe disk path (for example, `/mnt` or `/mnt/nvme0n1`) in the Pod spec.
+To use this method, specify the NVMe disk path (for example, `/mnt/nvme0n1`) in the Pod spec.
 
 #### Advantages
 

articles/aks/includes/windows-annual-channel-retirement.md

@@ -0,0 +1,15 @@
+---
+ms.service: azure-kubernetes-service
+ms.topic: include
+ms.date: 02/05/2026
+author: schaffererin
+ms.author: schaffererin
+---
+
+> [!IMPORTANT]
+> Starting on **May 15, 2026**, AKS no longer supports Windows Server Annual Channel (Preview). AKS will no longer produce new Windows Server Annual Channel node images or provide security patches. You won't be able to create new node pools with Windows Server Annual Channel. On **May 15, 2027**, AKS will remove all existing Windows Server Annual Channel node images, which will cause scaling and remediation (reimage and redeploy) operations to fail. To avoid disruption, we recommend migrating to the [Long Term Servicing Channel (LTSC)](/azure/aks/upgrade-windows-os).
+>
+> - Windows Server Annual Channel uses Windows Server 2022 base images, which will run on Windows Server 2022 and Windows Server 2025.
+> - If you're using [Host Process Containers (HPC)](../use-windows-hpc.md) or running other privileged containers for administration purposes, you need to do extra testing.
+>
+> For more information on this retirement, see the [Retirement GitHub issue](https://aka.ms/aks/windows-annual-channel-retirement). To stay informed on announcements and updates, follow the [AKS release notes](https://github.com/Azure/AKS/releases).

articles/aks/managed-gateway-api.md

@@ -1,124 +1,132 @@
 ---
-title: Azure Kubernetes Service (AKS) Managed Gateway API Installation
-description: Install Managed Kubernetes Gateway API on Azure Kubernetes Service
+title: Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview)
+description: Learn how to install the Kubernetes Gateway API Custom Resource Definitions (CRDs) on your Azure Kubernetes Service (AKS) cluster using the Managed Gateway API installation.
 ms.topic: how-to
 ms.service: azure-kubernetes-service
 author: nshankar
 ms.author: nshankar
+ms.reviewer: schaffererin
 ms.date: 01/26/2026
 # Customer intent: "As a Kubernetes administrator, I want to install the Kubernetes Gateway API Custom Resource Definitions (CRDs) to create Kubernetes Gateway API resources on my cluster."
 ---
 
-# Install Managed Gateway API CRDs (Preview)
+# Install Managed Gateway API CRDs on Azure Kubernetes Service (AKS) (preview)
 
-[!INCLUDE [preview features callout](~/reusable-content/ce-skilling/azure/includes/aks/includes/preview/preview-callout.md)]
+The [Kubernetes Gateway API][kubernetes-gateway-api] is a specification for traffic management on Kubernetes clusters. The specification enhances [Ingress API][kubernetes-ingress-api], which lacks a unified and provider-agnostic approach for advanced traffic routing.
 
-The [Kubernetes Gateway API][kubernetes-gateway-api] is a specification for traffic management on Kubernetes clusters. It was designed as a successor and enhancement of the [Ingress API][kubernetes-ingress-api], which lacked a unified and provider-agnostic approach for advanced traffic routing.
+The Managed Gateway API Installation for Azure Kubernetes Service (AKS) installs the Custom Resource Definitions (CRDs) for the Kubernetes Gateway API. With the Managed Gateway API installation, you can use Gateway API functionality in a fully supported mode on AKS.
 
-The Managed Gateway API Installation for Azure Kubernetes Service (AKS) installs the Custom Resource Definitions (CRDs) for the Kubernetes Gateway API. With the Managed Gateway API installation, you can use Gateway API functionality in a fully supported mode on AKS. However, you must also use an AKS add-on or extension that implements the Gateway API, such as the [Istio add-on][istio-gateway-api].
+## Prerequisites
 
-## Gateway API bundle version and AKS Kubernetes version mapping
+- You must use an AKS add-on or extension that implements the Gateway API, such as the [Istio add-on][istio-gateway-api]. If using the Istio add-on, you must be on minor revision `asm-1-26` or later to ensure compatibility with the Managed Gateway API installation. To deploy this add-on, see [Deploy Istio-based service mesh add-on for Azure Kubernetes Service (AKS)][istio-deploy].
 
-The following table outlines the supported Kubernetes versions for your AKS cluster for each Gateway API bundle version for the `standard` channel. `Experimental` channel CRDs are disallowed and must be uninstalled before enabling the Managed Gateway API installation.
+  - If you already have an existing installation of the Gateway API CRDs on your cluster, you must meet the following requirements:
 
-| Gateway API Bundle Version | Supported Kubernetes Versions |
-|----------------------------|-------------------------------|
-| v1.2.1                     | v1.26.0 - v1.33.x             |
-| v1.3.0                     | v1.34.0+                      |
+    - Only `standard` channel CRDs can be installed on your cluster. `Experimental` channel CRDs are disallowed, and you must uninstall them before enabling the Managed Gateway API.
+    - The Gateway API bundle version must be compatible with your cluster's Kubernetes version. For more information, see the [Supported Kubernetes versions for Gateway API bundle versions](#supported-kubernetes-versions-for-gateway-api-bundle-versions) section.
 
-> [!NOTE]
-> If you upgrade your AKS cluster to a new minor version after installing the Managed Gateway API CRDs, the CRDs will automatically be upgraded to the new supported Gateway API bundle version for that Kubernetes version. For instance, if you upgrade from AKS `v1.33.0` to `v1.34.0` and previously had the Managed Gateway API installed for bundle version `v1.2.1`, the CRDs are automatically upgraded to bundle version `v1.3.0`.
+- The [`aks-preview` extension installed and updated to version `19.0.0b4` or later](#install-or-update-the-aks-preview-extension).
+- The [`ManagedGatewayAPIPreview` feature flag registered to your subscription](#register-the-managed-gateway-api-preview-feature-flag).
 
-## Prerequisites
+### Install or update the `aks-preview` extension
 
-Ensure that you have at least one of the following implementations of the Gateway API installed and enabled on your cluster:
+[!INCLUDE [preview features callout](~/reusable-content/ce-skilling/azure/includes/aks/includes/preview/preview-callout.md)]
 
-* [Istio add-on][istio-deploy] minor revision `asm-1-26` and later.
+- Install the `aks-preview` extension or update to the latest version of the extension using the [`az extension add`][az-extension-add] and [`az extension update`][az-extension-update] commands. if you're using Azure CLI. You must use `aks-preview` version `19.0.0b4` and later.
 
-  * If you already have an existing installation of the Gateway API CRDs on your cluster, then you must only have `standard` channel CRDs installed, and the Gateway API bundle version must be compatible with your cluster's Kubernetes version. See the table for the [bundle version associated with each Kubernetes version](#gateway-api-bundle-version-and-aks-kubernetes-version-mapping).
+    ```azurecli-interactive
+    # Install the aks-preview extension
+    az extension add --name aks-preview
+    
+    # Update the aks-preview extension to the latest version
+    az extension update --name aks-preview
+    ```
 
-* Install the `aks-preview` extension using the [`az extension add`][az-extension-add] command if you're using Azure CLI. You must use `aks-preview` version `19.0.0b4` and later.
+### Register the Managed Gateway API preview feature flag
 
-  ```azurecli-interactive
-  az extension add --name aks-preview
-  ```
+- Register the `ManagedGatewayAPIPreview` feature flag using the [`az feature register`](/cli/azure/feature#az-feature-register) command.
 
-  Update to the latest version of the extension using the [`az extension update`][az-extension-update] command:
+    ```azurecli-interactive
+    az feature register --namespace "Microsoft.ContainerService" --name "ManagedGatewayAPIPreview"
+    ```
 
-  ```azurecli-interactive
-  az extension update --name aks-preview
-  ```
+## Supported Kubernetes versions for Gateway API bundle versions
 
-## Manage the Managed Gateway API preview feature
+The following table outlines the supported Kubernetes versions for your AKS cluster for each Gateway API bundle version for the `standard` channel:
 
-You can register the `ManagedGatewayAPIPreview` feature flag by using the [`az feature register`](/cli/azure/feature#az-feature-register) command:
+| Gateway API bundle version | Supported Kubernetes versions |
+|----------------------------|-------------------------------|
+| v1.2.1                     | v1.26.0 - v1.33.x             |
+| v1.3.0                     | v1.34.0+                      |
 
-```azurecli-interactive
-az feature register --namespace "Microsoft.ContainerService" --name "ManagedGatewayAPIPreview"
-```
+> [!NOTE]
+> If you upgrade your AKS cluster to a new minor version after installing the Managed Gateway API CRDs, the CRDs automatically upgrade to the new supported Gateway API bundle version for that Kubernetes version. For instance, if you upgrade from AKS `v1.33.0` to `v1.34.0` and previously had the Managed Gateway API installed for bundle version `v1.2.1`, the CRDs automatically upgrade to bundle version `v1.3.0`.
 
-Then you can install or uninstall the Managed Gateway API CRDs.
+## Create a new AKS cluster with Managed Gateway API CRDs installed
 
-# [Install CRDs](#tab/install)
+- Create a new AKS cluster with Managed Gateway API CRDs installed using the [`az aks create`][az-aks-create] command with the `--enable-gateway-api` flag. You can also enable a supported add-on, such as the Istio service mesh add-on, in the same command. The following example command creates a new AKS cluster with the Managed Gateway API installation and the Istio service mesh add-on enabled:
 
-1. You can run the [`az aks create`][az-aks-create] command to install the Managed Gateway API CRDs on a newly created cluster. You must also enable an implementation of the Gateway API to enable the managed CRD installation.
+    ```azurecli-interactive
+    az aks create --resource-group myResourceGroup --name myAKSCluster --enable-gateway-api --enable-azure-service-mesh
+    ```
 
-   ```azurecli-interactive
-   # Example: enable the managed Gateway API installation with the Istio service mesh add-on
-   az aks create -g $RESOURCE_GROUP -n $CLUSTER_NAME --enable-gateway-api --enable-azure-service-mesh
-   ```
+## Install Managed Gateway API CRDs on an existing AKS cluster
 
-1. To install the Managed Gateway API CRDs on an existing cluster with a supported implementation enabled, run the following command:
+- Install Managed Gateway API CRDs on an existing cluster with a supported implementation enabled using the [`az aks update`][az-aks-update] command with the `--enable-gateway-api` flag.
 
-   ```azurecli-interactive
-   az aks update -g $RESOURCE_GROUP -n $CLUSTER_NAME --enable-gateway-api
-   ```
+    ```azurecli-interactive
+    az aks update --resource-group myResourceGroup --name myAKSCluster --enable-gateway-api
+    ```
 
-1. To view the CRDs installed on your cluster, run the following command:
+## Verify Managed Gateway API CRD installation
+
+1. View the CRDs installed on your cluster using the following `kubectl get crds` command:
 
    ```bash
    kubectl get crds | grep "gateway.networking.k8s.io"
    ```
 
-   ```output
-   gatewayclasses.gateway.networking.k8s.io                           2025-08-29T17:52:36Z
-   gateways.gateway.networking.k8s.io                                 2025-08-29T17:52:36Z
-   grpcroutes.gateway.networking.k8s.io                               2025-08-29T17:52:36Z
-   httproutes.gateway.networking.k8s.io                               2025-08-29T17:52:37Z
-   referencegrants.gateway.networking.k8s.io                          2025-08-29T17:52:37Z
-   ```
+    The output should show the installed CRDs, which are part of the Kubernetes Gateway API specification. For example:
 
-1. Verify that the CRDs have the expected annotations and that the bundle version matches the [expected Kubernetes version](#gateway-api-bundle-version-and-aks-kubernetes-version-mapping) for your cluster.
+    ```output
+    gatewayclasses.gateway.networking.k8s.io                           2025-08-29T17:52:36Z
+    gateways.gateway.networking.k8s.io                                 2025-08-29T17:52:36Z
+    grpcroutes.gateway.networking.k8s.io                               2025-08-29T17:52:36Z
+    httproutes.gateway.networking.k8s.io                               2025-08-29T17:52:37Z
+    referencegrants.gateway.networking.k8s.io                          2025-08-29T17:52:37Z
+    ```
 
-   ```bash
-   kubectl get crd gateways.gateway.networking.k8s.io -ojsonpath={.metadata.annotations} | jq
-   ```
+1. Verify the CRDs have the expected annotations and the bundle version matches the [expected Kubernetes version](#supported-kubernetes-versions-for-gateway-api-bundle-versions) for your cluster using the following `kubectl get crds` command:
 
-   ```output
-   {
-     "api-approved.kubernetes.io": "https://github.com/kubernetes-sigs/gateway-api/pull/3328",
-     "app.kubernetes.io/managed-by": "aks",
-     "app.kubernetes.io/part-of": <hash>,
-     "gateway.networking.k8s.io/bundle-version": "v1.2.1",
-     "gateway.networking.k8s.io/channel": "standard"
-   }
-   ```
+    ```bash
+    kubectl get crd gateways.gateway.networking.k8s.io -ojsonpath={.metadata.annotations} | jq
+    ```
 
-# [Uninstall CRDs](#tab/uninstall)
+    The output should show the expected annotations, including the `gateway.networking.k8s.io/bundle-version` annotation with the expected bundle version for your cluster's Kubernetes version. For example, if your cluster is running Kubernetes `v1.33.0`, the expected bundle version is `v1.2.1`, and the output should be similar to the following:
 
-To uninstall the Managed Gateway API CRDs, run the [`az aks update`][az-aks-update] command:
+    ```output
+    {
+    "api-approved.kubernetes.io": "https://github.com/kubernetes-sigs/gateway-api/pull/3328",
+    "app.kubernetes.io/managed-by": "aks",
+    "app.kubernetes.io/part-of": <hash>,
+    "gateway.networking.k8s.io/bundle-version": "v1.2.1",
+    "gateway.networking.k8s.io/channel": "standard"
+    }
+    ```
 
-```azurecli-interactive
-az aks update -g $RESOURCE_GROUP -n $CLUSTER_NAME --disable-gateway-api
-```
+## Uninstall Managed Gateway API CRDs on an AKS cluster
 
----
+- Uninstall Managed Gateway API CRDs on an existing cluster using the [`az aks update`][az-aks-update] command with the `--disable-gateway-api` flag.
+
+    ```azurecli-interactive
+    az aks update --resource-group myResourceGroup --name myAKSCluster --disable-gateway-api
+    ```
 
-## Next Steps
+## Related content
 
-* [Configure ingress for Istio service mesh add-on with the Kubernetes Gateway API][istio-gateway-api]
+- [Configure ingress for Istio service mesh add-on with the Kubernetes Gateway API][istio-gateway-api]
 
-[istio-about]: ./istio-about.md
+<!-- LINKS -->
 [istio-deploy]: ./istio-deploy-addon.md
 [istio-gateway-api]: ./istio-gateway-api.md
 [az-aks-create]: /cli/azure/aks#az-aks-create