Skip to content

Commit f6dcd49

Browse files
sethmanheimsethmanheim
authored
Sync release-local-2504 with main
Sync release-local-2504 with main
2 parents 144988d + be22a53 commit f6dcd49

8 files changed

+153
-46
lines changed

‎AKS-Arc/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -333,6 +333,8 @@
333333
href: vnet.yml
334334
- name: AKS on Windows Server
335335
items:
336+
- name: AKS on Windows Server retirement
337+
href: aks-windows-server-retirement.md
336338
- name: Overview
337339
href: overview.md
338340
- name: System requirements

‎AKS-Arc/aks-windows-server-retirement.md

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
---
2+
title: Retirement of AKS architecture on Windows Server 2019 and Windows Server 2022
3+
description: Learn about retirement of AKS on Windows Server 2019 and Windows Server 2022.
4+
ms.topic: how-to
5+
ms.custom: linux-related-content
6+
author: sethmanheim
7+
ms.author: sethm
8+
ms.date: 03/26/2025
9+
10+
# Intent: As an IT Pro, I want to move my workloads from AKS on Windows Server to the latest version of AKS on Azure Local.
11+
# Keyword: retirement
12+
---
13+
14+
# Announcing the 3-year retirement of AKS on Windows Server current architecture
15+
16+
AKS enabled by Azure Arc uses Azure Arc to create new Kubernetes clusters on Azure Local directly from Azure. It enables you to use familiar tools such as the Azure portal, Azure CLI, Azure Resource Manager, and Bicep and Terraform templates to create and manage your Kubernetes clusters running on Azure Local. Microsoft continues to focus on delivering consistent user experience for all your AKS clusters. To continue ensuring Azure remains the best possible experience with the highest standards of safety and reliability, **we are retiring the current architecture of AKS on Windows Server 2019 and AKS on Windows Server 2022 in 3 years, on March 27, 2028**.
17+
18+
## What is AKS on Azure Local?
19+
20+
AKS on Azure Local uses Azure Arc to create new Kubernetes clusters on Azure Local directly from Azure. Since clusters are automatically connected to Azure Arc when they're created, you can use your Microsoft Entra ID for connecting to your clusters from anywhere. This ensures your developers and application operators can provision and configure Kubernetes clusters in accordance with company policies.
21+
22+
The following Kubernetes cluster deployment and management capabilities are available:
23+
24+
- **Pricing**: AKS is now included in Azure Local pricing, effective January 2025. This means that you only need to pay for Azure Local. There are no separate costs for running AKS clusters, including Linux and Windows node pools.
25+
- **Simplified infrastructure deployment on Azure Local**. Infrastructure components of AKS Arc like Arc Resource Bridge, Custom Location and the Kubernetes Extension for the AKS Arc operator, are all deployed as part of the Azure Local. The whole lifecycle management of AKS Arc infrastructure follows the same approach as the other components on Azure Local.
26+
- **Cloud-based management**: Create and manage Kubernetes clusters on Azure Local with familiar tools such as the Azure portal, Azure CLI, Azure Resource Manager, and Bicep and Terraform templates.
27+
- **Arc Gateway integration**: Deploy AKS Arc clusters with pod-level Arc Proxy and communicate with the Arc gateway, reducing the list of outbound URLs to configure in an isolated network environment.
28+
- **Integration with Entra ID and Azure RBAC**: Enable Azure RBAC for Kubernetes while creating AKS Arc clusters. Deploy AKS Arc clusters with workload identity enabled and deploy application pods with the workload identity label to access Microsoft Entra ID protected resources, such as Azure Key Vault.
29+
- **Support for NVIDIA T4**: Create Linux node pools in new VM sizes with GPU NVIDIA T4.
30+
- **K8s Audit Logs**: Export audit logs and other control plane logs to one or more destinations.
31+
- **Improved certificate management**: Shut down AKS Arc clusters for up to 7 days without any certificate expiration issues. Automatically repair certificates, managed by cert-tattoo, that expired when the cluster was shut down.
32+
33+
## If you're using Azure Kubernetes Service on Windows Server 2019 or Windows Server 2022
34+
35+
The Azure Kubernetes Service current architecture on Windows Server 2019 and Windows Server 2022 will be retired on 27 March 2028. Starting on March 27 2028, you no longer get support, security and quality updates for your existing Azure Kubernetes Service clusters. Additionally, you won't be able to deploy, upgrade or scale the current architecture of Azure Kubernetes Service on Windows Server 2019 and Windows Server 2022.
36+
37+
## If you're using Azure Kubernetes Service on Azure Local, version 22H2
38+
39+
If you're using AKS on Azure Local, version 22H2, be aware that Azure Local, version 22H2 will reach end of service on May 31 2025. After that, you won't receive monthly security and quality updates that provide protection from the latest security threats. To continue receiving updates, we recommend updating to the latest version of Azure Local.
40+
41+
## Deploy AKS on Azure Local, version 23H2 or later
42+
43+
### [From Windows Server 2019, 2022](#tab/ws)
44+
45+
AKS on Azure Local has a dependency on deploying a supported version of Azure Local. This means that local, PowerShell, or Windows Admin Center commands such as `Update-AksHciCluster` that worked on Windows Server don't work on Azure Local, version 23H2 or later, since AKS deployments on Azure Local, version 23H2 or later are managed via Azure Resource Manager (Azure CLI, Azure portal, etc.).
46+
47+
#### Evaluate if Azure Local is right for you
48+
49+
[Compare Windows Server](/azure/azure-local/concepts/compare-windows-server) explains key differences between Azure Local and Windows Server and provides guidance on when to use each. Both products are actively supported and maintained by Microsoft. Many organizations choose to deploy both, as they are intended for different and complementary purposes.
50+
51+
#### Uninstall AKS on Windows Server
52+
53+
Before you move to Azure Local, follow these steps to disconnect AKS workload clusters from Azure Arc and then uninstall AKS:
54+
55+
- Identify all your Arc-connected AKS workload clusters, and then [disconnect your AKS workload clusters from Azure Arc](connect-to-arc.md#disconnect-your-aks-cluster-from-azure-arc)
56+
- Uninstall AKS using [`Uninstall-AksHci`](/azure/aks/aksarc/reference/ps/uninstall-akshci). This removes all AKS-related configuration from Windows Server.
57+
58+
#### Deploy a supported version of Azure Local
59+
60+
[Deploy Azure Local from Azure portal or an Azure Resource Manager template](/azure/azure-local/deploy/deployment-introduction).
61+
62+
#### Deploy an AKS cluster on Azure Local
63+
64+
- [Review the networking pre-requisites](aks-hci-network-system-requirements.md) for deploying AKS on Azure Local.
65+
- [Deploy an AKS cluster on Azure Local using Az CLI, Azure portal and ARM templates, etc.](aks-create-clusters-cli.md).
66+
67+
### [From Azure Local, version 22H2](#tab/22H2)
68+
69+
AKS on Azure Local has a dependency on deploying a supported version of Azure Local. This means that local, PowerShell, or Windows Admin Center commands such as `Update-AksHciCluster` that worked on Azure Local, version 22H2 don't work on Azure Local, version 23H2 or later, since AKS deployments on Azure Local, version 23H2 or later are managed via Azure Resource Manager (Az CLI, Azure portal, etc).
70+
71+
#### Uninstall AKS on Azure Local, version 22H2
72+
73+
Before you upgrade to a supported version of Azure Local, follow these steps to disconnect AKS workload clusters from Azure Arc and then uninstall AKS:
74+
75+
- Identify all your Arc-connected AKS workload clusters, and then [disconnect your AKS workload clusters from Azure Arc](connect-to-arc.md#disconnect-your-aks-cluster-from-azure-arc)
76+
- Uninstall AKS using [`Uninstall-AksHci`](/azure/aks/aksarc/reference/ps/uninstall-akshci). This removes all AKS-related configuration from Windows Server.
77+
78+
#### Upgrade to a supported version of Azure Local
79+
80+
[Upgrade Azure Local 22H2 to a supported version of Azure Local](/azure/azure-local/upgrade/about-upgrades-23h2).
81+
82+
#### Deploy an AKS cluster on Azure Local
83+
84+
- [Review the networking pre-requisites](aks-hci-network-system-requirements.md) for deploying AKS on Azure Local.
85+
- [Deploy an AKS cluster on Azure Local using Az CLI, Azure portal and ARM templates, etc.](aks-create-clusters-cli.md).
86+
87+
---
88+
89+
## Next steps
90+
91+
- [Compare AKS deployment options](https://techcommunity.microsoft.com/blog/azurearcblog/comparing-feature-sets-for-aks-enabled-by-azure-arc-deployment-options/4188163).
92+
- [Compare Windows Server with Azure Local](/azure/azure-local/concepts/compare-windows-server)

‎AKS-Arc/concepts-storage.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,6 @@ ms.reviewer: abha
1616
# Storage options for applications in AKS enabled by Azure Arc
1717

1818
[!INCLUDE [hci-applies-to-23h2](includes/hci-applies-to-23h2.md)]
19-
[!INCLUDE [applies-to-azure stack-hci-and-windows-server-skus](includes/aks-hci-applies-to-skus/aks-hybrid-applies-to-azure-stack-hci-windows-server-sku.md)]
2019

2120
Applications that run in AKS deployments using Azure Kubernetes Service enabled by Azure Arc might need to store and retrieve data. For some application workloads, the data can use local, fast storage on an unneeded node when the pods are deleted (Kubernetes uses _pods_ to run an instance of an application).
2221

‎AKS-Arc/create-clusters-terraform.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ For more options, you can either follow [Configure SSH keys for an AKS cluster](
5353

5454
## Sign in to Azure
5555

56-
Terraform only supports authenticating to Azure with the Azure CLI using [`az login`](/cli/azure/reference-index#az-login). Authenticating using Azure PowerShell isn't supported. Therefore, while you can use the Azure PowerShell module when doing your Terraform work, you must first [authenticate to Azure](/azure/developer/terraform/authenticate-to-azure):
56+
Terraform only supports authenticating to Azure with the Azure CLI using [`az login`](/cli/azure/reference-index#az-login). Authenticating using Azure PowerShell isn't supported. Therefore, while you can use the Azure PowerShell module when doing your Terraform work, you must first [authenticate to Azure](/azure/developer/terraform/authenticate-to-azure):
5757

5858
```azurecli
5959
az login
@@ -62,7 +62,7 @@ az login
6262
## Implement the Terraform code
6363

6464
1. Create a directory you can use to test the sample Terraform code, and make it your current directory.
65-
1. In the same directory, create a file named **providers.tf** and paste the following code:
65+
1. In the same directory, create a file named **providers.tf** and paste the following code. Make sure to replace `<subscription_ID>` with your subscription ID:
6666

6767
```terraform
6868
terraform {
@@ -79,7 +79,8 @@ az login
7979
}
8080
}
8181
82-
provider "azurerm" {
82+
provider "azurerm" {
83+
subscription_id = "<subscription_ID>"
8384
features {
8485
resource_group {
8586
prevent_deletion_if_contains_resources = false

‎AKS-Arc/deploy-ai-model.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to deploy an AI model on AKS Arc with the Kubernetes AI t
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: how-to
7-
ms.date: 03/21/2025
7+
ms.date: 03/25/2025
88
ms.reviewer: haojiehang
99
ms.lastreviewed: 12/03/2024
1010

@@ -66,7 +66,7 @@ To create a GPU node pool using the Azure portal, follow these steps:
6666

6767
### [Azure CLI](#tab/azurecli)
6868

69-
To create a GPU node pool using Azure CLI, run the following command. The GPU VM SKU used in the following example is for the **A16** model; for the full list of VM SKUs, see [Supported VM sizes](scale-requirements.md#supported-vm-sizes).
69+
To create a GPU node pool using Azure CLI, run the following command. The GPU VM SKU used in the following example is for the **A16** model; for the full list of VM SKUs, see [Supported VM sizes](deploy-gpu-node-pool.md#supported-gpu-vm-sizes).
7070

7171
```azurecli
7272
az aksarc nodepool add --name "samplenodepool" --cluster-name "samplecluster" --resource-group "sample-rg" --node-vm-size "Standard_NC16_A16" --os-type "Linux"

‎AKS-Arc/deploy-gpu-node-pool.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use GPUs for compute-intensive workloads (AKS on Azure Local, version 23H
33
description: Learn how to deploy GPU-enabled node pools in AKS enabled by Arc.
44
author: sethmanheim
55
ms.topic: how-to
6-
ms.date: 03/21/2025
6+
ms.date: 03/25/2025
77
ms.author: sethm
88
ms.lastreviewed: 03/21/2025
99
ms.reviewer: abha
@@ -21,6 +21,8 @@ ms.reviewer: abha
2121
2222
Graphical Processing Units (GPU) are used for compute-intensive workloads such as machine learning, deep learning, and more. This article describes how to use GPUs for compute-intensive workloads in AKS enabled by Azure Arc.
2323

24+
[!INCLUDE [supported-gpu-models](includes/supported-gpu-models.md)]
25+
2426
## Before you begin
2527

2628
To use GPUs in AKS Arc, make sure you installed the necessary GPU drivers before you begin the deployment of the cluster. Follow the steps in this section.

‎AKS-Arc/includes/supported-gpu-models.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
author: sethmanheim
3+
ms.author: sethm
4+
ms.topic: include
5+
ms.date: 03/25/2025
6+
ms.reviewer: abha
7+
ms.lastreviewed: 03/25/2025
8+
9+
---
10+
11+
## Supported GPU models
12+
13+
The following GPU models are supported by AKS on Azure Local, version 23H2:
14+
15+
| Manufacturer | GPU model | Supported version |
16+
|--------------|-----------|-------------------|
17+
| NVidia | A2 | 2311.2 |
18+
| NVidia | A16 | 2402.0 |
19+
| NVidia | T4 | 2408.0 |
20+
21+
## Supported GPU VM sizes
22+
23+
The following VM sizes for each GPU model are supported by AKS on Azure Local, version 23H2.
24+
25+
### Nvidia T4 is supported by NK T4 SKUs
26+
27+
| VM size | GPUs | GPU Memory: GiB | vCPU | Memory: GiB |
28+
|-----------------|---|----|-----|----|
29+
| Standard_NK6 | 1 | 8 | 6 | 12 |
30+
| Standard_NK12 | 2 | 16 | 12 | 24 |
31+
32+
### Nvidia A2 is supported by NC2 A2 SKUs
33+
34+
| VM size | GPUs | GPU Memory: GiB | vCPU | Memory: GiB |
35+
|-------------------|---|----|----|----|
36+
| Standard_NC4_A2 | 1 | 16 | 4 | 8 |
37+
| Standard_NC8_A2 | 1 | 16 | 8 | 16 |
38+
| Standard_NC16_A2 | 2 | 32 | 16 | 64 |
39+
| Standard_NC32_A2 | 2 | 32 | 32 | 128 |
40+
41+
### Nvidia A16 is supported by NC2 A16 SKUs
42+
43+
| VM size | GPUs | GPU Memory: GiB | vCPU | Memory: GiB |
44+
|--------------------|---|----|----|----|
45+
| Standard_NC4_A16 | 1 | 16 | 4 | 8 |
46+
| Standard_NC8_A16 | 1 | 16 | 8 | 16 |
47+
| Standard_NC16_A16 | 2 | 32 | 16 | 64 |
48+
| Standard_NC32_A16 | 2 | 32 | 32 | 128 |

‎AKS-Arc/scale-requirements.md

Lines changed: 2 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Scale requirements for AKS on Azure Local
33
description: Learn about scale requirements for AKS on Azure Local.
44
ms.topic: conceptual
5-
ms.date: 03/24/2025
5+
ms.date: 03/25/2025
66
author: sethmanheim
77
ms.author: sethm
88
ms.reviewer: abha
@@ -66,44 +66,7 @@ This article describes the maximum and minimum supported scale count for AKS on
6666

6767
For more worker node sizes with GPU support, see the next section.
6868

69-
## Supported GPU models
70-
71-
The following GPU models are supported by AKS on Azure Local, version 23H2:
72-
73-
| Manufacturer | GPU model | Supported version |
74-
|--------------|-----------|-------------------|
75-
| NVidia | A2 | 2311.2 |
76-
| NVidia | A16 | 2402.0 |
77-
| NVidia | T4 | 2408.0 |
78-
79-
## Supported VM sizes
80-
81-
The following VM sizes for each GPU models are supported by AKS on Azure Local, version 23H2.
82-
83-
### Nvidia T4 is supported by NK T4 SKUs
84-
85-
| VM size | GPUs | GPU Memory: GiB | vCPU | Memory: GiB |
86-
|-----------------|---|----|-----|----|
87-
| Standard_NK6 | 1 | 8 | 6 | 12 |
88-
| Standard_NK12 | 2 | 16 | 12 | 24 |
89-
90-
### Nvidia A2 is supported by NC2 A2 SKUs
91-
92-
| VM size | GPUs | GPU Memory: GiB | vCPU | Memory: GiB |
93-
|-------------------|---|----|----|----|
94-
| Standard_NC4_A2 | 1 | 16 | 4 | 8 |
95-
| Standard_NC8_A2 | 1 | 16 | 8 | 16 |
96-
| Standard_NC16_A2 | 2 | 32 | 16 | 64 |
97-
| Standard_NC32_A2 | 2 | 32 | 32 | 128 |
98-
99-
### Nvidia A16 is supported by NC2 A16 SKUs
100-
101-
| VM size | GPUs | GPU Memory: GiB | vCPU | Memory: GiB |
102-
|--------------------|---|----|----|----|
103-
| Standard_NC4_A16 | 1 | 16 | 4 | 8 |
104-
| Standard_NC8_A16 | 1 | 16 | 8 | 16 |
105-
| Standard_NC16_A16 | 2 | 32 | 16 | 64 |
106-
| Standard_NC32_A16 | 2 | 32 | 32 | 128 |
69+
[!INCLUDE [supported-gpu-models](includes/supported-gpu-models.md)]
10770

10871
## Next steps
10972

0 commit comments

Comments
 (0)