More articles

Author: sethmanheim

AKS-Arc/app-availability.md

@@ -1,9 +1,9 @@
 ---
-title: Application availability in AKS enabled by Azure Arc
-description: Learn about application availability in AKS enabled by Arc
+title: Application availability in AKS on Windows Server
+description: Learn about application availability in on Windows Server.
 author: sethmanheim
 ms.topic: conceptual
-ms.date: 04/01/2025
+ms.date: 04/07/2025
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
 ms.reviewer: rbaziwane
@@ -12,11 +12,11 @@ ms.reviewer: rbaziwane
 # Keyword: AKS on Windows Server architecture live migration disruption Kubernetes container orchestration
 ---
 
-# Application availability in AKS enabled by Azure Arc
+# Application availability in 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)]
 
-Azure Kubernetes Service (AKS) enabled by Azure Arc offers a fully supported container platform that can run cloud-native applications on the [Kubernetes container orchestration platform](https://kubernetes.io/). The architecture supports running virtualized Windows and Linux workloads.
+Azure Kubernetes Service (AKS) on Windows Server offers a fully supported container platform that can run cloud-native applications on the [Kubernetes container orchestration platform](https://kubernetes.io/). The architecture supports running virtualized Windows and Linux workloads.
 
 The AKS architecture is built with failover clustering and live migration that is automatically enabled for target (workload) clusters. During various disruption events, virtual machines that host customer workloads are freely moved around without perceived application downtime. This architecture means that a traditional enterprise customer, who's managing a legacy application as a singleton to AKS on Windows Server, gets similar (or better) uptime than what's currently experienced on a legacy VM application.
 

AKS-Arc/concepts-cluster-autoscaling.md

@@ -1,23 +1,23 @@
 ---
-title: Cluster autoscaling in AKS enabled by Azure Arc
-description: Learn about automatically scaling node pools in AKS enabled by Azure Arc
+title: Cluster autoscaling in AKS on Windows Server
+description: Learn about automatically scaling node pools in AKS on Windows Server.
 ms.topic: conceptual
 author: sethmanheim
 ms.author: sethm 
-ms.date: 04/04/2025
+ms.date: 04/07/2025
 
 # Intent: As a Kubernetes user, I want to use cluster autoscaler to grow my nodes to keep up with application demand.
 # Keyword: cluster autoscaling
 
 ---
 
-# Cluster autoscaling in AKS enabled by Azure Arc
+# Cluster autoscaling in 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)]
 
 You can adjust the number of nodes that run application workloads in AKS Arc by using Azure Kubernetes Service (AKS) to keep up with demand. You can use PowerShell to enable the autoscaler and to manage automatic scaling of node pools in your target clusters.
 
-This article describes the context of the autoscaler in AKS enabled by Arc, and how the autoscaler works. For cluster autoscaling to work effectively, you can also use the Kubernetes horizontal pod autoscaler, which is a standard Kubernetes component. For more information about the Kubernetes horizontal pod autoscaler, see [Horizontal pod autoscaling](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/).
+This article describes the context of the autoscaler in AKS on Windows Server, and how the autoscaler works. For cluster autoscaling to work effectively, you can also use the Kubernetes horizontal pod autoscaler, which is a standard Kubernetes component. For more information about the Kubernetes horizontal pod autoscaler, see [Horizontal pod autoscaling](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/).
 
 ## Cluster autoscaling
 

AKS-Arc/concepts-container-networking.md

@@ -1,9 +1,9 @@
 ---
 title: Container networking concepts
-description: Learn about container networking in AKS enabled by Azure Arc.
+description: Learn about container networking in AKS on Windows Server.
 author: sethmanheim
 ms.topic: conceptual
-ms.date: 04/01/2025
+ms.date: 04/07/2025
 ms.author: sethm 
 ms.lastreviewed: 05/31/2022
 
@@ -20,7 +20,7 @@ Application components must work together to process their tasks in a container-
 
 More complex applications might require configuration of ingress traffic for SSL/TLS termination or routing of multiple components. You might also need to restrict the flow of network traffic into or between pods and nodes for security.
 
-This article introduces the core concepts that provide networking to your applications in AKS enabled by Arc:
+This article introduces the core concepts that provide networking to your applications in AKS on Windows Server:
 
 - Kubernetes services
 - Ingress controller

AKS-Arc/concepts-node-networking.md

@@ -1,9 +1,9 @@
 ---
-title: Node virtual machine networking in AKS enabled by Azure Arc
+title: Node virtual machine networking in AKS on Windows Server
 description: Learn about virtual machine networking in AKS Arc, including static IP and DHCP networking and load balancers.
 author: sethmanheim
 ms.topic: conceptual
-ms.date: 04/01/2025
+ms.date: 04/07/2025
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
 
@@ -15,7 +15,7 @@ ms.lastreviewed: 1/14/2022
 
 [!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)]
 
-You can choose between two IP address assignment models for your networking architecture for AKS enabled by Arc. AKS supports [several deployment options](aks-overview.md) for Azure Kubernetes Service (AKS):
+You can choose between two IP address assignment models for your networking architecture for AKS on Windows Server. AKS supports [several deployment options](aks-overview.md) for Azure Kubernetes Service (AKS):
 
 - **Static IP networking**: the virtual network allocates static IP addresses to the Kubernetes cluster API server, Kubernetes nodes, underlying VMs, load balancers, and any Kubernetes services that run on top of the cluster.
 - **DHCP networking**: the virtual network allocates dynamic IP addresses to the Kubernetes nodes, underlying VMs, and load balancers using a DHCP server. The Kubernetes cluster API server, and any Kubernetes services you run on top of your cluster, are still allocated static IP addresses.
@@ -143,7 +143,7 @@ As you can see, the number of required IP addresses is variable depending on the
 
 ### Walk through an example deployment
 
-Jane is an IT administrator just starting with AKS enabled by Azure Arc. She wants to deploy two Kubernetes clusters: Kubernetes cluster A and Kubernetes cluster B on her Windows Server cluster. She also wants to run a voting application on top of her cluster. This application has three instances of the front-end UI running across the two clusters and one instance of the backend database.
+Jane is an IT administrator just starting with AKS on Windows Server. She wants to deploy two Kubernetes clusters: Kubernetes cluster A and Kubernetes cluster B on her Windows Server cluster. She also wants to run a voting application on top of her cluster. This application has three instances of the front-end UI running across the two clusters and one instance of the backend database.
 
 - Kubernetes cluster A has 3 control plane nodes and 5 worker nodes.
 - Kubernetes cluster B has 1 control plane node and 3 worker nodes.

AKS-Arc/concepts-vertical-node-pool-scaling.md

@@ -1,11 +1,10 @@
 ---
-title: Vertical node scaling in AKS enabled by Azure Arc
-description: Learn about the vertical scaling of node pools in AKS enabled by Arc.
+title: Vertical node scaling in AKS on Windows Server
+description: Learn about the vertical scaling of node pools in AKS on Windows Server.
 ms.topic: conceptual
 author: sethmanheim
 ms.author: sethm 
-ms.lastreviewed: 06/26/2024
-ms.reviewer: mikek
+ms.lastreviewed: 04/07/2025
 ms.date: 10/21/2022
 
 # Intent: As a Kubernetes user, I want to use increase my VM size in place to grow my nodes to keep up with application demand.
@@ -16,7 +15,7 @@ ms.date: 10/21/2022
 
 [!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)]
 
-You can change the size of the virtual machines in a given node pool, to increase the resources available to the node pool in AKS enabled by Azure Arc.
+You can change the size of the virtual machines in a given node pool, to increase the resources available to the node pool in AKS on Windows Server.
 
 To keep up with app demands in Azure Kubernetes Service (AKS), you might need to adjust the number of nodes that run your workloads. In some cases, scaling a cluster horizontally by adding nodes isn't sufficient to meet the demands from your app for more CPU cores or memory.
 

AKS-Arc/node-repair.md

@@ -1,6 +1,6 @@
 ---
 title: Node auto-repair
-description: Learn about automatic node repair of Windows and Linux nodes in AKS enabled by Azure Arc.
+description: Learn about automatic node repair of Windows and Linux nodes in AKS on Windows Server.
 author: sethmanheim
 ms.topic: how-to
 ms.custom: linux-related-content
@@ -15,7 +15,7 @@ ms.reviewer: oadeniji
 
 [!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)]
 
-To help minimize service disruptions for clusters, AKS enabled by Azure Arc continuously monitors the health state of worker nodes, and performs automatic node repair if issues arise or if they become unhealthy. This article describes how AKS Arc checks for unhealthy nodes and automatically repairs both Windows and Linux nodes. The article also shows how to manually check node health.
+To help minimize service disruptions for clusters, AKS on Windows Server continuously monitors the health state of worker nodes, and performs automatic node repair if issues arise or if they become unhealthy. This article describes how AKS Arc checks for unhealthy nodes and automatically repairs both Windows and Linux nodes. The article also shows how to manually check node health.
 
 ## How AKS checks for unhealthy nodes
 

AKS-Arc/pricing.md

@@ -1,7 +1,7 @@
 ---
 
-title: Azure Kubernetes Service (AKS) enabled by Azure Arc pricing details
-description: Learn about detailed pricing information for AKS enabled by Azure Arc.
+title: Azure Kubernetes Service (AKS) on Windows Server pricing details
+description: Learn about detailed pricing information for AKS on Windows Server.
 ms.topic: conceptual
 author: sethmanheim
 ms.author: sethm 
@@ -15,18 +15,18 @@ ms.reviewer: rbaziwane
 ---
 
 
-# AKS enabled by Azure Arc pricing details
+# AKS on Windows Server pricing details
 
-> Applies to: AKS on Windows Server
+[!INCLUDE [aks-hybrid-applies-to-azure-stack-hci-windows-server-sku](includes/aks-hci-applies-to-skus/aks-hybrid-applies-to-azure-stack-hci-windows-server-sku.md)]
 
-Azure Kubernetes Service (AKS) enabled by Azure Arc is a subscription-based Kubernetes offering that can be run on Windows Server Hyper-V clusters. You can download and install AKS Arc on your existing hardware either in your own on-premises data center, or on the edge. The pricing is based on usage and requires an Azure subscription, which you can obtain for free. The billing unit is a virtual core or vCPU. All initial AKS deployments include a free 60-day evaluation period, at the end of which a pay-as-you-go rate per vCPU (of running worker nodes) per day is applied.
+Azure Kubernetes Service (AKS) on Windows Server is a subscription-based Kubernetes offering that can be run on Windows Server Hyper-V clusters. You can download and install AKS Arc on your existing hardware either in your own on-premises data center, or on the edge. The pricing is based on usage and requires an Azure subscription, which you can obtain for free. The billing unit is a virtual core or vCPU. All initial AKS deployments include a free 60-day evaluation period, at the end of which a pay-as-you-go rate per vCPU (of running worker nodes) per day is applied.
 
 > [!IMPORTANT]
-> Starting in June 2023, we have made revisions that solidify the 60-day evaluation period as a one-time benefit per subscription, at the end of which a pay-as-you-go rate per vCPU will apply. This modification means the evaluation period no longer resets when you reinstall AKS enabled by Azure Arc. This change is being made to better align with our existing pricing guidelines and to ensure the continued provision of high-quality services.
+> Starting in June 2023, we have made revisions that solidify the 60-day evaluation period as a one-time benefit per subscription, at the end of which a pay-as-you-go rate per vCPU will apply. This modification means the evaluation period no longer resets when you reinstall AKS on Windows Server. This change is being made to better align with our existing pricing guidelines and to ensure the continued provision of high-quality services.
 
 ## Pricing details
 
-Azure pricing for running workloads on AKS enabled by Arc is based on US currency list pricing with:
+Azure pricing for running workloads on AKS on Windows Server is based on US currency list pricing with:
 
 - Pay-as-you-go pricing
 - D-series general purpose VM sizes (D2s v4, D4s V4, and D8s V4)