Merge pull request #15394 from sethmanheim/fresh6-26

AKS freshness reviews

Author: sethmanheim

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

@@ -4,7 +4,7 @@ description: Learn about the vertical scaling of node pools in AKS enabled by Ar
 ms.topic: conceptual
 author: sethmanheim
 ms.author: sethm 
-ms.lastreviewed: 03/18/2022
+ms.lastreviewed: 06/26/2024
 ms.reviewer: mikek
 ms.date: 10/21/2022
 
@@ -16,11 +16,11 @@ 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 your 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 enabled by Azure Arc.
 
 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.
 
-Without vertical node scaling, you would have to redeploy to a new node pool and move the app. This situation might not be ideal in resource limited edge environments. To enable this flexibility, AKS Arc introduces the capability to change the virtual machine (VM) size (SKU) of the VMs in a given node pool.
+Without vertical node scaling, you must redeploy to a new node pool and move the app. This situation might not be ideal in resource limited edge environments. To enable this flexibility, AKS Arc introduces the capability to change the virtual machine (VM) size (SKU) of the VMs in a given node pool.
 
 ## How vertical node scaling in AKS Arc works
 
@@ -31,7 +31,7 @@ To change the node pool to a different VM size (SKU), you can use the `Set-AksHc
 When you submit the command with the new VM size (SKU), a new **machineDeployment** for the node pool or cluster is created, replacing the existing machine set. This event triggers an update flow in the underlying deployment system. Similar to an OS or Kubernetes version upgrade, the new **machineDeployment** uses a rolling update to replace one virtual machine in the node pool or control plane after the other. Each upgrade checks that the old node is correctly cordoned and drained before it's removed.
 
 > [!NOTE]
-> The system assumes that you have checked that enough hardware resources are available to scale up the new machine set in place of the old machine set.
+> The system assumes that enough hardware resources are available to scale up the new machine set in place of the old machine set.
 
 ## Example process
 

AKS-Hybrid/create-daemonsets.md

@@ -3,7 +3,7 @@ title: Create a Kubernetes DaemonSet in AKS enabled by Azure Arc
 description: Learn how to create a DaemonSet in Azure Kubernetes Service (AKS) enabled by Azure Arc.
 author: sethmanheim
 ms.topic: how-to
-ms.date: 10/21/2022
+ms.date: 06/26/2024
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
 ms.reviewer: EkeleAsonye
@@ -17,15 +17,15 @@ ms.reviewer: EkeleAsonye
 
 [!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 describes how to create and use a Kubernetes _DaemonSet_ in AKS enabled by Azure Arc to ensure that a copy of a pod is always available on every worker node in a cluster. You can use a DaemonSet to improve cluster performance by ensuring that an app runs on all the worker nodes, and to deploy pods that do maintenance and provide support services for nodes.
+This article describes how to create and use a Kubernetes *DaemonSet* in AKS enabled by Azure Arc to ensure that a copy of a pod is always available on every worker node in a cluster. You can use a DaemonSet to improve cluster performance by ensuring that an app runs on all the worker nodes, and to deploy pods that do maintenance and provide support services for nodes.
 
 ## Overview of DaemonSets
 
-**DaemonSet** is a Kubernetes object that ensures a copy of a pod that's defined in the configuration is always available on every worker node in a cluster. When a new node is added to a cluster, the DaemonSet automatically allocates the pod on that node.
+A DaemonSet is a Kubernetes object that ensures a copy of a pod that's defined in the configuration is always available on every worker node in a cluster. When a new node is added to a cluster, the DaemonSet automatically allocates the pod on that node.
 
 Similarly, when a node is deleted, the pod that's running on the node is also deleted and isn't rescheduled on another node (for example, as happens with **ReplicaSets**). This enables you to overcome Kubernetes scheduling limitations and make sure a specific application is deployed on all nodes within the cluster.
 
-DaemonSets can improve the overall cluster performance. For example, you can use them to deploy pods to perform maintenance tasks and support services to every node: 
+DaemonSets can improve the overall cluster performance. For example, you can use them to deploy pods to perform maintenance tasks and support services to every node:
 
 - Run a log collection daemon, such as `Fluentd` and `Logstash`.
 - Run a node monitoring daemon, such as `Prometheus`.
@@ -73,7 +73,7 @@ You can update a DaemonSet using the `kubectl edit ds<NAME>` command. However, i
 
 ## Delete a DaemonSet
 
-To remove a DaemonSet, use the `kubectl delete` command (for example, `kubectl delete –f example-daemon.yaml -n monitoring`). You should be cautious when specifying the name of the DaemonSet file as deleting a DaemonSet cleans up all the pods it deployed.
+To remove a DaemonSet, use the `kubectl delete` command (for example, `kubectl delete –f example-daemon.yaml -n monitoring`). You should be cautious when specifying the name of the DaemonSet file, as deleting a DaemonSet cleans up all the pods it deployed.
 
 ## Next steps
 

AKS-Hybrid/create-deployments.md

@@ -3,7 +3,7 @@ title: Create deployments in AKS enabled by Azure Arc
 description: Learn how to create deployments in Azure Kubernetes Service (AKS) Arc.
 author: sethmanheim
 ms.topic: how-to
-ms.date: 10/21/2022
+ms.date: 06/26/2024
 ms.author: sethm 
 ms.lastreviewed: 03/04/2022
 ms.reviewer: EkeleAsonye
@@ -15,7 +15,7 @@ ms.reviewer: EkeleAsonye
 
 [!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 an overview of Kubernetes deployments and describes how to create and update deployments in AKS enabled by Azure Arc.
+This article provides an overview of Kubernetes deployments, and describes how to create and update these deployments in AKS enabled by Azure Arc.
 
 ## Kubernetes deployments overview
 

AKS-Hybrid/create-replicasets.md

@@ -3,7 +3,7 @@ title: Create a ReplicaSet in AKS enabled by Azure Arc
 description: Learn how to create a ReplicaSet in Azure Kubernetes Service (AKS) enabled by Arc.
 author: sethmanheim
 ms.topic: how-to
-ms.date: 10/21/2022
+ms.date: 06/26/2024
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
 ms.reviewer: EkeleAsonye

AKS-Hybrid/create-statefulset.md

@@ -3,7 +3,7 @@ title: Create StatefulSets in AKS enabled by Azure Arc
 description: Learn how to create StatefulSets in Azure Kubernetes Service (AKS) enabled by Arc.
 author: sethmanheim
 ms.topic: how-to
-ms.date: 10/21/2022
+ms.date: 06/26/2024
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
 ms.reviewer: EkeleAsonye
@@ -27,7 +27,7 @@ The main components of StatefulSets are the persistent volume provisioner and th
 
 ## How to create a StatefulSet
 
-You create a StatefulSet using the `kubectl create` or the `kubectl apply` command. For example:
+You can create a StatefulSet using the `kubectl create` or the `kubectl apply` command. For example:
 
 ```powershell
 kubectl create –f statefulset.yaml

AKS-Hybrid/deploy-azure-container-registry.md

@@ -3,7 +3,7 @@ title: Deploy from a private container registry to on-premises Kubernetes using
 description: Learn how to deploy from a private container registry to on-premises Kubernetes using Azure Container Registry and AKS enabled by Arc.
 author: sethmanheim
 ms.topic: how-to
-ms.date: 11/02/2022
+ms.date: 06/26/2024
 ms.author: sethm
 ms.lastreviewed: 03/16/2022
 ms.reviewer: rbaziwane
@@ -20,7 +20,7 @@ This article describes how to deploy container images from a private container r
 
 The article describes how to create a private container registry in Azure and push your container image to the private container registry. You can then deploy from the private registry to your on-premises Kubernetes cluster hosted in AKS enabled by Arc.
 
-If you're interested in learning more about Container Registry in Azure, see the [Azure Container Registry documentation](/azure/container-registry/).
+For more information about Container Registry in Azure, see the [Azure Container Registry documentation](/azure/container-registry/).
 
 ## Prerequisites
 
@@ -39,7 +39,7 @@ In order to create a container registry, begin with a *resource group*. An Azure
 az group create --name <RESOURCE_GROUP_NAME> --location eastus
 ```
 
-Create a Container Registry instance with the [az acr create](/cli/azure/acr) command, and provide your own registry name. The registry name must be unique within Azure and contain 5 to 50 alphanumeric characters. In the rest of this article, `<acrName>` is used as a placeholder for the container registry name, but you can provide your own unique registry name. The Basic SKU is a cost-optimized entry point for development purposes that provides a balance of storage and throughput.
+Create a Container Registry instance with the [az acr create](/cli/azure/acr) command, and provide your own registry name. The registry name must be unique within Azure and contain 5 to 50 alphanumeric characters. In the rest of this article, `<acrName>` is used as a placeholder for the container registry name, but you can provide your own unique registry name. The Basic SKU is a cost-optimized entry point for development purposes that provides a balance of storage and throughput:
 
 ```azurecli
 az acr create --resource-group <RESOURCE_GROUP_NAME> --name <REGISTRY_NAME> --sku Basic

AKS-Hybrid/deploy-windows-application.md

@@ -3,7 +3,7 @@ title: Deploy Windows .NET applications
 description: Learn how to deploy a Windows.NET application to your Kubernetes cluster using a custom image stored in Azure Container Registry in AKS enabled by Azure Arc.
 author: sethmanheim
 ms.topic: tutorial
-ms.date: 11/01/2022
+ms.date: 06/26/2024
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
 ms.reviewer: abha
@@ -17,7 +17,7 @@ ms.reviewer: abha
 
 [!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 tutorial describes how to deploy an ASP.NET sample application in a Windows Server container to the Azure Kubernetes Service (AKS) cluster in AKS enabled by Arc, and then test and scale your application. You also learn how to join a Windows node to an Active Directory domain.
+This tutorial describes how to deploy an ASP.NET sample application in a Windows Server container to the Azure Kubernetes Service (AKS) cluster in AKS enabled by Arc, then test and scale your application. You also learn how to join a Windows node to an Active Directory domain.
 
 This tutorial assumes a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for AKS enabled by Azure Arc](kubernetes-concepts.md).
 
@@ -31,7 +31,7 @@ Make sure you met the following requirements:
 
 When you follow the procedures:
 
-- Run the commands in a PowerShell administrative window.
+- Run the commands in a PowerShell administrator window.
 - Ensure that OS-specific workloads land on the appropriate container host. If your Kubernetes cluster has a mixture of Linux and Windows worker nodes, you can use either node selectors or taints and tolerations. For more information, see [using node selectors and taints and tolerations](adapt-apps-mixed-os-clusters.md).
 
 ## Deploy the application
@@ -92,7 +92,7 @@ spec:
 
 Deploy the application using the `kubectl apply` command, and specify the name of your YAML manifest:
 
-```console
+```powershell
 kubectl apply -f sample.yaml
 ```
 
@@ -109,11 +109,11 @@ When the application runs, a Kubernetes service exposes the application front en
 
 To monitor progress, use the `kubectl get service` command with the `--watch` argument:
 
-```PowerShell
+```powershell
 kubectl get service sample --watch
 ```
 
-Initially, the **EXTERNAL-IP** for the **sample** service is shown as **pending**.
+Initially, the **EXTERNAL-IP** for the **sample** service is shown as **pending**:
 
 ```output
 NAME    TYPE           CLUSTER-IP   EXTERNAL-IP   PORT(S)        AGE
@@ -137,19 +137,19 @@ If the connection times out when you try to load the page, verify whether the sa
 
 We created a single replica of the application front end. To see the number and state of pods in your cluster, use the `kubectl get` command as follows:
 
-```console
+```powershell
 kubectl get pods -n default
 ```
 
 To change the number of pods in the **sample** deployment, use the `kubectl scale` command. The following example increases the number of front-end pods to 3:
 
-```console
+```powershell
 kubectl scale --replicas=3 deployment/sample
 ```
 
 Run `kubectl get pods` again to verify that the pods were created. After a minute or so, the additional pods are available in your cluster:
 
-```console
+```powershell
 kubectl get pods -n default
 ```
 

AKS-Hybrid/monitor-logging.md

@@ -3,7 +3,7 @@ title: Monitoring and logging data
 description: Learn how to create and access monitor and logging data for AKS enabled by Azure Arc.
 author: sethmanheim
 ms.topic: how-to
-ms.date: 10/24/2022
+ms.date: 06/26/2024
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
 ms.reviewer: abha

AKS-Hybrid/multiple-load-balancers.md

@@ -1,9 +1,9 @@
 ---
 title: Use multiple load balancers
-description: How to use multiple load balancer instances and scale the numbers of instances on your Azure Kubernetes Service (AKS) deployment in AKS enabled by Azure Arc.
+description: How to use multiple load balancer instances and scale the numbers of instances on your AKS deployment in AKS enabled by Azure Arc.
 author: sethmanheim
 ms.author: sethm
-ms.date: 10/21/2022 
+ms.date: 06/26/2024
 ms.reviewer: rbaziwane
 ms.lastreviewed: 07/29/2022
 ms.topic: how-to
@@ -17,7 +17,7 @@ ms.topic: how-to
 
 [!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 describes how to deploy one or more instances of the **HAProxy** load balancer in AKS enabled by Azure Arc, and how to scale out or in the load balancer configuration in the target cluster.
+This article describes how to deploy one or more instances of the **HAProxy** load balancer in AKS enabled by Azure Arc, and how to scale the load balancer configuration in the target cluster.
 
 In AKS enabled by Arc, the load balancer is deployed as a virtual machine (VM) running Linux and **HAProxy + KeepAlive** to provide load balanced services for the workload clusters. This VM is used to load balance requests to the Kubernetes API server and for handling traffic to application services.
 
@@ -49,9 +49,9 @@ To deploy multiple load balancers during the workload cluster creation, use the
 ## Scale out the load balancer instances
 
 > [!IMPORTANT]
-> Make sure you have enough physical memory and storage in your cluster before performing this operation. If the amount of physical memory required to deploy the requested number of load balancers is insufficient, this operation will fail.
+> Make sure you have enough physical memory and storage in your cluster before you perform this operation. If the amount of physical memory required to deploy the requested number of load balancers is insufficient, this operation will fail.
 
-To scale out (or in) your load balancer instances after deployment of a workload cluster, follow these steps:
+To scale your load balancer instances out (or in) after deployment of a workload cluster, follow these steps:
 
 1. Run `Set-AksHciLoadBalancer` with the number of instances you want to deploy in the cluster