Skip to content

Commit a6943f6

Browse files
Merge pull request #3751 from MicrosoftDocs/main638888008883045597sync_temp
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
2 parents 58ff6ee + d6ad5d6 commit a6943f6

File tree

5 files changed

+15
-13
lines changed

5 files changed

+15
-13
lines changed

AKS-Arc/TOC.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
href: data-collection.md
1414
- name: Blogs and announcements
1515
href: blogs-announcements.md
16-
- name: AKS on Azure Local
16+
- name: AKS Arc on Azure Local
1717
expanded: true
1818
items:
1919
- name: What's new in AKS on Azure Local
@@ -332,7 +332,7 @@
332332
href: aks-edge-licensing.md
333333
- name: Microsoft Software License Terms
334334
href: aks-edge-software-license-terms.md
335-
- name: AKS on VMware
335+
- name: AKS Arc on VMware
336336
items:
337337
- name: Overview
338338
href: aks-vmware-overview.md
@@ -380,7 +380,7 @@
380380
href: vmsize.yml
381381
- name: vnet
382382
href: vnet.yml
383-
- name: AKS on Windows Server
383+
- name: AKS Arc on Windows Server
384384
items:
385385
- name: AKS on Windows Server retirement
386386
href: aks-windows-server-retirement.md
@@ -390,7 +390,7 @@
390390
href: system-requirements.md
391391
- name: Quickstarts
392392
items:
393-
- name: Deploy an AKS cluster
393+
- name: Deploy an AKS Arc cluster
394394
items:
395395
- name: Use PowerShell
396396
href: kubernetes-walkthrough-powershell.md

AKS-Arc/aks-whats-new-local.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: What's new in AKS on Azure Local
33
description: Learn about what's new in AKS on Azure Local.
44
ms.topic: overview
5-
ms.date: 07/21/2025
5+
ms.date: 07/22/2025
66
author: sethmanheim
77
ms.author: sethm
88
ms.reviewer: rcheeran
@@ -34,6 +34,7 @@ The following Kubernetes cluster deployment and management capabilities are avai
3434

3535
- **Disk space exhaustion**: Fixed [issues due to disk space exhaustion on control plane VMs due to accumulation of kube-apiserver audit logs](kube-apiserver-log-overflow.md).
3636
- **Cluster upgrade**: Fixed AKS Arc cluster and node pool create, scale, and [upgrade issues due to unavailability of AKS Arc VM images](gallery-image-not-usable.md).
37+
- **AKS Arc Telemetry pod issue**: Fixed an issue in which the [AKS Arc telemetry pod was consuming excessing CPU and memory](telemetry-pod-resources.md).
3738
- **New checks**: Added new checks during cluster and node pool operations. These improvements allow the system to proactively detect and handle scenarios where there are insufficient IP addresses in the IP pool.
3839
- **GPU resource allocation**: Additional pre-checks for resource allocation for GPUs during Kubernetes cluster create operation.
3940
- **Node pool improvements**: Accurate representation of node pool count and status on the Azure portal. This release also includes improvements to node pool creation and update flows to ensure that the Kubernetes cluster status accounts for corresponding node pool status.

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
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.
2+
title: Retirement of AKS architecture on Windows Server
3+
description: Learn about the retirement of AKS on Windows Server.
44
ms.topic: how-to
55
ms.custom: linux-related-content
66
author: sethmanheim
77
ms.author: sethm
8-
ms.date: 07/21/2025
8+
ms.date: 07/22/2025
99
ms.reviewer: rcheeran
1010
ms.lastreviewed: 07/21/2025
1111

@@ -37,7 +37,7 @@ The following Kubernetes cluster deployment and management capabilities are avai
3737

3838
## If you're using Azure Kubernetes Service on Windows Server 2019 or Windows Server 2022
3939

40-
The AKS Arc current architecture on Windows Server 2019 and Windows Server 2022 will be retired on March 27, 2028. Starting on March 27 2028, you no longer get support, security and quality updates for your existing AKS Arc clusters. You also won't be able to deploy, upgrade or scale the current architecture of Azure Kubernetes Service on Windows Server 2019 and Windows Server 2022.
40+
The AKS Arc current architecture on Windows Server 2019 and Windows Server 2022 will be retired on March 27, 2028. Starting on March 27 2028, you no longer get support, security and quality updates for your existing AKS Arc clusters. You also won't be able to deploy, upgrade or scale the current architecture of Azure Kubernetes Service on Windows Server 2019 and Windows Server 2022. Between now and March 2028, we will not add support for any new Windows Server SKUs; for example, Windows Server 2025 is not supported on AKS Arc.
4141

4242
## If you're using Azure Kubernetes Service on Azure Local, version 22H2
4343

AKS-Arc/gallery-image-not-usable.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,9 @@ description: Learn about a known issue with Kubernetes cluster create or nodepoo
44
ms.topic: troubleshooting
55
author: sethmanheim
66
ms.author: sethm
7-
ms.date: 07/17/2025
7+
ms.date: 07/22/2025
88
ms.reviewer: rcheeran
9+
ms.lastreviewed: 07/22/2025
910

1011
---
1112

@@ -47,8 +48,8 @@ This issue was fixed in [AKS on Azure Local, version 2507](/azure/azure-local/wh
4748

4849
- Upgrade your Azure Local deployment to the 2507 build.
4950
- Once updated, confirm that the images were downloaded successfully by running the `az aksarc get-versions` command.
50-
- For new AKS clusters: new AKS clusters should now be created successfully.
51-
- For scaling existing AKS clusters: scaling existing AKS clusters continues to encounter issues. Please file a support case.
51+
- You can now use the specified Kubernetes versions while creating or updating your AKS Arc clusters.
52+
- If you continue to encounter issues, please file a support ticket.
5253

5354
## Next steps
5455

azure-local/known-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ The following table lists the known issues in this release:
135135
| Update <!--33470082--> | Solution update fails with the error: `Unable to install solution update "11.2506.1001.24" - Type 'UpdateFOD' of Role 'ComposedImageUpdate' raised an exception.` | For detailed steps on how to resolve this issue, see the [Troubleshooting guide](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/SolutionUpdate-UpdateFOD.md). |
136136
| Deployment <!--33471589--> | After Azure portal deployment, SConfig network settings shows the error: `Set-SCfNetworksetting : Cannot bind argument to parameter 'Value' because it is null.` | There's no known workaround in this release. |
137137
| Update <!--33448368--> | Cluster-Aware Updating runs might fail with the error:<br>`Type 'SBEPartnerConfirmCauDone' of Role 'SBE' raised an exception:<br>SBE_MsftCIOnlyCommon_CommonForTesting_4.2.2504.16: ErrorID: SBE-CAU-RUNNING-AFTER-DONE -- CAU run is still in progress when it should be done. See https://aka.ms/AzureLocal/SBE/CauHelp for help. Review full Get-CauRun output it identify if it is progressing or stuck. Wait for it to complete if progressing.` | Wait for CAU run to complete (wait for `Get-CauRun` to report `RunNotInProgress`) and resume the update. |
138-
|Azure Local VMs <!--33811472-->| When no storage path is specified during deployment, resources (VMs, data disks, and images) are automatically placed on the first storage path of the cluster, even when other storage paths are also available. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. | Update to Azure Local 2507, which includes a fix for this issue. Or, create resources with a specified storage path. For more information, see [Troubleshoot Azure Local Virtual Machines enabled by Azure Arc](../azure-local/manage/troubleshoot-arc-enabled-vms.md#resource-deployment-failure-due-to-insufficient-disk-space-on-the-first-storage-path). |
138+
|Azure Local VMs <!--33811472-->| When no storage path is specified during deployment, resources (VMs, data disks, and images) are automatically placed on the first storage path of the cluster, even when other storage paths are also available. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. | Create resources with a specified storage path. For more information, see [Troubleshoot Azure Local Virtual Machines enabled by Azure Arc](../azure-local/manage/troubleshoot-arc-enabled-vms.md#resource-deployment-failure-due-to-insufficient-disk-space-on-the-first-storage-path). |
139139

140140
## Known issues from previous releases
141141

0 commit comments

Comments
 (0)