More

Author: sethmanheim

AKS-Arc/TOC.yml

@@ -357,7 +357,7 @@
         href: tutorial-kubernetes-prepare-application.md
       - name: 2 - Create container registry
         href: tutorial-kubernetes-prepare-azure-container-registry.md
-      - name: 3 - Deploy a workload cluster
+      - name: 3 - Deploy a Kubernetes cluster
         href: tutorial-kubernetes-deploy-cluster.md
       - name: 4 - Run an application
         href: tutorial-kubernetes-deploy-application.md

AKS-Arc/concepts-support.md

@@ -1,6 +1,6 @@
 ---
-title: Tested resource limits, VM sizes, and regions for AKS enabled by Azure Arc
-description: Resource limits, VM sizes, regions for Azure Kubernetes Service (AKS) enabled by Azure Arc.
+title: Tested resource limits, VM sizes, and regions for AKS on Windows Server
+description: Resource limits, VM sizes, regions for Azure Kubernetes Service (AKS) on Windows Server.
 author: sethmanheim
 ms.topic: conceptual
 ms.date: 03/31/2025
@@ -13,15 +13,15 @@ ms.custom: references_regions
 
 ---
 
-# Resource limits, VM sizes, and regions for AKS enabled by Azure Arc
+# Resource limits, VM sizes, and regions for AKS on Windows Server
 
 [!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)]
 
-This article provides information about tested configurations, resource limits, VM sizes, and regions for Azure Kubernetes Service (AKS) enabled by Azure Arc. The tests used the latest release of AKS enabled by Azure Arc.
+This article provides information about tested configurations, resource limits, VM sizes, and regions for Azure Kubernetes Service (AKS) on Windows Server. The tests used the latest release of AKS on Windows Server.
 
 ## Maximum specifications
 
-AKS enabled by Arc deployments have been validated with the following configurations, including the specified maximums. Keep in mind that exceeding these maximums is at your own risk and might lead to unexpected behaviors and failures. This article provides some guidance on how to avoid common configuration mistakes and can help you create a larger configuration. If in doubt, contact your local Microsoft office for assistance or [submit a question to the community](https://feedback.azure.com/d365community/search/?q=Azure+Kubernetes).
+AKS on Windows Server deployments have been validated with the following configurations, including the specified maximums. Keep in mind that exceeding these maximums is at your own risk and might lead to unexpected behaviors and failures. This article provides some guidance on how to avoid common configuration mistakes and can help you create a larger configuration. If in doubt, contact your local Microsoft office for assistance or [submit a question to the community](https://feedback.azure.com/d365community/search/?q=Azure+Kubernetes).
 
 | Resource                     | Maximum |
 | ---------------------------- | --------|
@@ -46,7 +46,7 @@ The hardware configuration of each physical node in the AKS Arc cluster is as fo
 - Disk: 8x HDDs (2 TB or larger) and 2x 1.6 TB NVMe to support S2D storage configurations.
 - Network: Four (4) 100-Gbit NICs (Mellanox or Intel).
 
-Microsoft engineering tested AKS enabled by Arc using the above configuration. For single node. 2 node, 4 node and 8 node Windows failover clusters. If you have a requirement to exceed the tested configuration, see [Scaling AKS](#scaling-aks).
+Microsoft engineering tested AKS on Windows Server using this configuration, for single node, 2 node, 4 node, and 8 node Windows failover clusters. If you have a requirement that exceeds the tested configuration, see [Scaling AKS](#scaling-aks).
 
 > [!IMPORTANT]  
 > When you upgrade a deployment of AKS, extra resources are temporarily consumed.
@@ -79,7 +79,7 @@ The following VM sizes for control plane nodes, Linux worker nodes, and Windows
 
 ## Supported Azure regions for Azure registration
 
-AKS enabled by Arc is supported in the following Azure regions:
+AKS on Windows Server is supported in the following Azure regions:
 
 - Australia East
 - East US
@@ -171,7 +171,7 @@ The following scaling example is based on these general assumptions/use cases:
 - To run 200 worker nodes in one target cluster, you can use the default control plane and load balancer size. Depending on the number of pods per node, you can go up at least one size on the control plane and use **Standard_D8s_v3**.
 - Depending on the number of Kubernetes services hosted in each target cluster, you might have to increase the size of the load balancer VM as well at target cluster creation to ensure that services can be reached with high performance and traffic is routed accordingly.
 
-The deployment of AKS enabled by Arc distributes the worker nodes for each node pool in a target cluster across the available nodes using placement logic.
+The deployment of AKS on Windows Server distributes the worker nodes for each node pool in a target cluster across the available nodes using placement logic.
 
 > [!IMPORTANT]
 > The node placement is not preserved during platform and AKS upgrades and will change over time. A failed physical node also impacts the distribution of virtual machines across the remaining cluster nodes.

AKS-Arc/tutorial-kubernetes-deploy-cluster.md

@@ -1,6 +1,6 @@
 ---
-title: Deploy a workload cluster on AKS enabled by Azure Arc
-description: In this tutorial, learn how to create a Kubernetes cluster and use kubectl to connect to the Kubernetes master node in AKS enabled by Arc.
+title: Deploy a Kubernetes cluster on Windows Server
+description: In this tutorial, learn how to create a Kubernetes cluster and use kubectl to connect to the Kubernetes master node in AKS on Windows Server.
 ms.topic: tutorial
 ms.date: 04/03/2025
 ms.author: sethm 
@@ -13,7 +13,7 @@ author: sethmanheim
 
 ---
 
-# Tutorial: Deploy a workload cluster on AKS enabled by Arc
+# Tutorial: Deploy a Kubernetes cluster on Windows Server
 
 [!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)]
 
@@ -22,7 +22,7 @@ Kubernetes provides a distributed platform for containerized applications.
 In this tutorial, part three of seven, a Kubernetes cluster is deployed on AKS on Windows Server. You'll learn how to:
 
 > [!div class="checklist"]
-> * Deploy an AKS cluster on Windows Server
+> * Deploy a Kubernetes cluster on Windows Server
 > * Install the Kubernetes CLI (kubectl)
 > * Configure kubectl to connect to your workload cluster
 
@@ -156,9 +156,9 @@ moc-lel7tzxdt30   Ready    control-plane,master   6d20h   v1.20.7
 In this tutorial, a Kubernetes cluster was deployed in AKS, and you configured `kubectl` to connect to it. You learned how to:
 
 > [!div class="checklist"]
-> * Deploy an AKS cluster on Windows Server
+> * Deploy a Kubernetes cluster on Windows Server
 > * Install the Kubernetes CLI (kubectl)
-> * Configure kubectl to connect to your AKS cluster
+> * Configure kubectl to connect to your Kubernetes cluster
 
 Advance to the next tutorial to learn how to deploy an application to the cluster.
 

AKS-Arc/tutorial-kubernetes-upgrade-cluster.md

@@ -185,7 +185,7 @@ Remove-AksHciCluster -name mycluster
 
 ## Next steps
 
-In this tutorial, you upgraded Kubernetes in a Kubernetes cluster on AKS enabled by Arc. You learned how to:
+In this tutorial, you upgraded a Kubernetes cluster on Windows Server. You learned how to:
 
 > [!div class="checklist"]
 > * Identify current and available Kubernetes versions