Freshness top 40

Author: sethmanheim

AKS-Arc/aks-create-clusters-portal.md

@@ -4,7 +4,7 @@ description: Create Kubernetes clusters using the Azure portal.
 author: sethmanheim
 ms.author: sethm
 ms.topic: how-to
-ms.date: 01/30/2024
+ms.date: 02/20/2025
 ms.reviewer: guanghu
 ms.lastreviewed: 01/30/2024
 ---
@@ -29,7 +29,7 @@ This article describes how to create Kubernetes clusters in Azure Local using th
 ## Create a Kubernetes cluster
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
-1. On the Azure portal search bar, type Kubernetes Azure Arc.
+1. On the Azure portal search bar, type **Kubernetes Azure Arc**.
 1. Select **Add > Create a Kubernetes cluster with Azure Arc**:
 
    :::image type="content" source="media/aks-create-clusters-portal/cluster-portal.png" alt-text="Screenshot showing cluster creation page on the portal." lightbox="media/aks-create-clusters-portal/cluster-portal.png":::

AKS-Arc/concepts-support.md

@@ -3,7 +3,7 @@ title: Tested resource limits, VM sizes, and regions for AKS enabled by Azure Ar
 description: Resource limits, VM sizes, regions for Azure Kubernetes Service (AKS) enabled by Azure Arc.
 author: sethmanheim
 ms.topic: conceptual
-ms.date: 12/21/2023
+ms.date: 02/20/2025
 ms.author: sethm 
 ms.lastreviewed: 02/03/2022
 ms.reviewer: mamezgeb

AKS-Arc/index.yml

@@ -9,7 +9,7 @@ metadata:
   ms.topic: landing-page
   author: sethmanheim
   ms.author: sethm 
-  ms.date: 02/15/2024
+  ms.date: 02/20/2025
 
 landingContent:
   - title: About AKS enabled by Azure Arc

AKS-Arc/overview.md

@@ -5,7 +5,7 @@ ms.topic: overview
 ms.custom: linux-related-content
 author: sethmanheim
 ms.author: sethm 
-ms.date: 01/29/2024
+ms.date: 02/20/2025
 
 # Intent: As an IT Pro, I want to use AKS on Azure Local and Windows Server to deploy on-premises Kubernetes and orchestrate containerized workloads.
 # Keyword: on-premises Kubernetes
@@ -15,21 +15,21 @@ ms.date: 01/29/2024
 
 [!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) on Azure Local and Windows Server is an on-premises Kubernetes implementation of AKS. AKS on Azure Local and Windows Server automates running containerized applications at scale. AKS makes it quicker to get started hosting Linux and Windows containers in your datacenter.
+Azure Kubernetes Service (AKS) on Azure Local and Windows Server is an on-premises Kubernetes implementation of AKS. AKS on Azure Local and Windows Server automates running containerized applications at scale. AKS on Azure Local and Windows Server makes it quicker to get started hosting Linux and Windows containers in your datacenter.
 
 To get started with on-premises Kubernetes using AKS, [set up AKS on Azure Local and Windows Server](setup.md).
 
 Or, you can use AKS to orchestrate your cloud-based containers. See [Azure Kubernetes Service in Azure](/azure/aks/intro-kubernetes).  If you're using Azure Stack Hub, see [AKS engine on Azure Stack Hub](/azure-stack/user/azure-stack-kubernetes-aks-engine-overview).
 
-The following sections discuss some of the reasons to use AKS on Azure Local and Windows Server, then answer some common questions about the service and how to get started. For a background on containers, see [Windows and containers](/virtualization/windowscontainers/about/).  For a background on how Kubernetes works in AKS on Azure Local and Windows Server, see [Kubernetes core concepts](kubernetes-concepts.md) and for a background on Kubernetes, see [Kubernetes.io](https://kubernetes.io).
+The following sections discuss some of the reasons to use AKS on Azure Local and Windows Server, then answer some common questions about the service and how to get started. For a background on containers, see [Windows and containers](/virtualization/windowscontainers/about/). For information about how Kubernetes works in AKS on Azure Local and Windows Server, see [Kubernetes core concepts](kubernetes-concepts.md). For more information about Kubernetes, see [the Kubernetes.io documentation](https://kubernetes.io).
 
 ## Why use AKS on Windows Server and Azure Local for containerized applications?
 
-While you can manage a few containers manually using Docker and Windows, apps often make use of five, ten, or even hundreds of containers, which are where the Kubernetes orchestrator comes in.
+While you can manage a few containers manually using Docker and Windows, apps often make use of five, ten, or even hundreds of containers, which is where the Kubernetes orchestrator comes in.
 
-Kubernetes is an open-source orchestrator for automating container management at scale. AKS simplifies on-premises Kubernetes deployment by providing wizards you can use to set up Kubernetes and essential Azure Local add-ons, and also create Kubernetes clusters to host your workloads.
+Kubernetes is an open-source orchestrator for automating container management at scale. AKS simplifies on-premises Kubernetes deployment by providing wizards you can use to set up Kubernetes and essential Azure Local add-ons, and also to create Kubernetes clusters to host your workloads.
 
-Here's some of the functionality AKS provides on Windows Server and Azure Local:
+Some of the functionality AKS provides on Windows Server and Azure Local includes:
 
 - Deploy containerized apps at scale to Kubernetes clusters running across the Azure Local and Windows Server cluster.
 - Deploy and manage both Linux and Windows-based containerized apps.
@@ -45,34 +45,34 @@ AKS simplifies the process of setting up Kubernetes on Azure Local and Windows S
 
 - A Windows Admin Center wizard for setting up AKS and its dependencies.
 - A Windows Admin Center wizard for creating Kubernetes clusters to run your containerized applications.
-- PowerShell cmdlets for setting up Kubernetes and creating Kubernetes clusters, in case you'd rather script the host setup and Kubernetes cluster creation.
+- PowerShell cmdlets for setting up Kubernetes and creating Kubernetes clusters, if you prefer to use a script to host setup and Kubernetes cluster creation.
 
-View the GIF below to familiarize yourself with the deployment process:
+View the following image to familiarize yourself with the deployment process:
 
 :::image type="content" source="media/overview/aks-hci-deployment.gif" alt-text="GIF showing AKS deployment." lightbox="media/overview/aks-hci-deployment.gif":::
 
 ## View and manage on-premises Kubernetes using tools or Azure Arc
 
-Once you've set up on-premises Kubernetes using AKS and created a Kubernetes cluster, you can manage and monitor your Kubernetes infrastructure with:
+Once you set up on-premises Kubernetes using AKS and create a Kubernetes cluster, you can manage and monitor your Kubernetes infrastructure with:
 
-- **In the Azure portal using Azure Arc** - Use Azure Arc to manage applications deployed on top of Kubernetes clusters across your cloud and on-premises environments.  
+- **The Azure portal using Azure Arc**: Use Azure Arc to manage applications deployed on top of Kubernetes clusters across your cloud and on-premises environments.  
   Azure Arc also enables you to manage your Kubernetes clusters with other Azure services including:
   - Azure Monitor
   - Azure Policy
-- **On-premises using popular tools like Kubectl** - There are many open-source tools that allow you to deploy applications to a Kubernetes cluster, manage cluster resources, troubleshoot, and view running applications. All of these tools work with Kubernetes clusters deployed with AKS on Azure Local and Windows Server.
+- **On-premises using popular tools such as Kubectl**: There are many open-source tools that allow you to deploy applications to a Kubernetes cluster, manage cluster resources, troubleshoot, and view running applications. All of these tools work with Kubernetes clusters deployed with AKS on Azure Local and Windows Server.
 
 ## Run Linux and Windows containers
 
-AKS fully supports both Linux-based and Windows-based containers. When you create a Kubernetes cluster on Windows Server or Azure Local, you can choose whether to create node pools (groups of identical Kubernetes cluster nodes) to run Linux containers, Windows containers, or both. 
+AKS fully supports both Linux-based and Windows-based containers. When you create a Kubernetes cluster on Windows Server or Azure Local, you can choose whether to create node pools (groups of identical Kubernetes cluster nodes) to run Linux containers, Windows containers, or both.
 
 AKS creates the Linux and Windows nodes so that you don't have to directly manage the Linux or Windows operating systems.
 
 ## Secure your container infrastructure
 
-AKS includes many features to help secure your container infrastructure:
+AKS includes features that can help to secure your container infrastructure:
 
-- **Hypervisor-based isolation for worker nodes** - Each Kubernetes cluster runs on its own dedicated and isolated set of virtual machines so tenants can share the same physical infrastructure.
-- **Microsoft-maintained Linux and Windows images for worker nodes** - Worker nodes run Linux and Windows virtual machine images created by Microsoft to adhere to security best practices. Microsoft also refreshes these images monthly with the latest security updates.
+- **Hypervisor-based isolation for worker nodes**: Each Kubernetes cluster runs on its own dedicated and isolated set of virtual machines so that tenants can share the same physical infrastructure.
+- **Microsoft-maintained Linux and Windows images for worker nodes**: Worker nodes run Linux and Windows virtual machine images created by Microsoft to adhere to security best practices. Microsoft also refreshes these images monthly with the latest security updates.
 
 ## What you need to get started
 
@@ -82,47 +82,49 @@ The following sections summarize what you need to run on-premises Kubernetes wit
 
 Your machine running the Windows Admin Center gateway must be:  
 
-- Registered with Azure
-- In the same domain as the Azure Local or Windows Server 2019/2022 Datacenter cluster
+- Registered with Azure.
+- In the same domain as the Azure Local or Windows Server 2019/2022 Datacenter cluster.
 
 ### On the Azure Local and Windows Server cluster or Windows Server 2019/2022 Datacenter failover cluster that hosts AKS
 
 The Azure Local and Windows Server cluster or Windows Server 2019/2022 Datacenter failover cluster has the following requirements:
 
-- A maximum of eight servers in the cluster
-- 1 TB of available capacity in the storage pool for AKS
-- At least 30 GB of available memory for running AKS VMs
-- All servers in the cluster must use the EN-US region and language selection
+- A maximum of eight servers in the cluster.
+- 1 TB of available capacity in the storage pool for AKS.
+- At least 30 GB of available memory for running AKS VMs.
+- All servers in the cluster must use the EN-US region and language selection.
 
-For general Azure Local system requirements, see [Azure Local system requirements](/azure-stack/hci/concepts/system-requirements).
+For general Azure Local system requirements, see [Azure Local system requirements](/azure/azure-local/concepts/system-requirements).
 
-### The network configuration for Azure Local
+### Network configuration for Azure Local
 
-The network connected to VMs on the Azure Local or Windows Server 2019/2022 Datacenter cluster requires a dedicated scope of IPv4 addresses available for AKS and accessible by VMs on the Azure Local or Windows Server 2019/2022 Datacenter cluster. For more information on networking requirements, see [AKS on Azure Local and Windows Server system requirements](system-requirements.md).
+The network connected to VMs on the Azure Local or Windows Server 2019/2022 Datacenter cluster requires a dedicated scope of IPv4 addresses available for AKS and accessible by VMs on the Azure Local or Windows Server 2019/2022 Datacenter cluster. For more information about networking requirements, see [AKS on Azure Local and Windows Server system requirements](system-requirements.md).
 
-Here's some of the functionality AKS provides:
+## AKS on Azure Local and Windows Server functionality
 
-## Native integration using Azure Arc
+The following sections describe some of the functionality AKS provides:
 
-With AKS, you can connect your Kubernetes clusters to Azure. Once connected to Azure Arc-enabled Kubernetes, you can access your Kubernetes clusters running on-premises via the Azure portal and deploy management services such as GitOps and Azure Policy. You can also deploy data services such as SQL Managed Instance and PostgreSQL Hyperscale. For more information about Azure Arc-enabled Kubernetes, see the [Azure Arc overview](/azure/azure-arc/kubernetes/overview).
+### Native integration using Azure Arc
 
-## Integrated logging and monitoring
+With AKS, you can connect your Kubernetes clusters to Azure. Once connected to Azure Arc-enabled Kubernetes, you can access your Kubernetes clusters running on-premises via the Azure portal, and deploy management services such as GitOps and Azure Policy. You can also deploy data services such as SQL Managed Instance and PostgreSQL Hyperscale. For more information about Azure Arc-enabled Kubernetes, see the [Azure Arc overview](/azure/azure-arc/kubernetes/overview).
 
-Once you've connected your cluster to Azure Arc, you can use Azure Monitor for monitoring the health of your Kubernetes cluster and applications. Azure Monitor for containers gives you performance visibility by collecting memory and processor metrics from controllers, nodes, and containers. Metrics and container logs are automatically collected for you and are sent to the metrics database in Azure Monitor, while log data is sent to your Log Analytics workspace. For more information about Azure Monitor, see the [container insights overview](/azure/azure-monitor/containers/container-insights-overview).
+### Integrated logging and monitoring
 
-## Software defined networking for your Kubernetes nodes and containerized applications
+Once you connect your cluster to Azure Arc, you can use Azure Monitor for monitoring the health of your Kubernetes cluster and applications. Azure Monitor for containers gives you performance visibility by collecting memory and processor metrics from controllers, nodes, and containers. Metrics and container logs are automatically collected for you and are sent to the metrics database in Azure Monitor, while log data is sent to your Log Analytics workspace. For more information about Azure Monitor, see the [container insights overview](/azure/azure-monitor/containers/container-insights-overview).
 
-With SDN integration on Azure Local, you can now bring in your own networks and attach the Kubernetes nodes to these networks. Additionally, you can use the SDN Software Load Balancer to provide load balancer services for their containerized applications. For more information, see [software defined networking with AKS](software-defined-networking.md).
+### Software defined networking for your Kubernetes nodes and containerized applications
 
-## Automatically resize your Kubernetes node pools
+With SDN integration on Azure Local, you can now bring your own networks and attach the Kubernetes nodes to these networks. Additionally, you can use the SDN Software Load Balancer to provide load balancer services for their containerized applications. For more information, see [software defined networking with AKS](software-defined-networking.md).
+
+### Automatically resize your Kubernetes node pools
 
 To keep up with application demands, you might need to adjust the number and size of nodes that run your workloads. The cluster autoscaler component can watch for pods in your cluster that can't be scheduled because of resource constraints. When issues are detected, the number of nodes in a node pool is increased to meet the application demand. Nodes are also regularly checked for a lack of running pods, with the number of nodes then decreased as needed. This ability to automatically scale up or down the number of nodes in your Kubernetes cluster lets you run an efficient, cost-effective environment.
 
-## Deploy and manage Windows-based containerized apps
+### Deploy and manage Windows-based containerized apps
 
 AKS fully supports running both Linux-based and Windows-based containers. When you create a Kubernetes cluster on Windows Server or Azure Local, you can choose whether to create node pools (groups of identical Kubernetes cluster nodes) to run Linux containers, Windows containers, or both. AKS creates the Linux and Windows nodes so that you don't have to directly manage the Linux or Windows operating systems.
 
-## AKS supports deploying GPU-enabled nodes
+### Deploy GPU-enabled nodes
 
 AKS supports deploying GPU-enabled node pools on top of NVIDIA Tesla T4 GPUs using Discrete Device Assignment (DDA) mode, also known as *GPU Passthrough*. In this mode, one or more physical GPUs are dedicated to a single worker node with a GPU enabled VM size which gets full access to the entire GPU hence offering high level application compatibility as well as better performance. For more information about GPU-enabled node pools, see the [GPU documentation](deploy-gpu-node-pool.md).