Merge pull request #16225 from v-thepet/aks-hci1

[bulk] Azure Stack HCI to Azure Local rebrand in AKS-Hybrid (a-i)

Author: JamesJBarnett

AKS-Hybrid/ad-sso.md

@@ -77,7 +77,7 @@ Before you can install AD authentication, the workload cluster must be installed
 
 #### Option 1
 
-For a domain-joined Azure Stack HCI or Windows Server cluster, open PowerShell as an administrator and run the following command:
+For a domain-joined Azure Local or Windows Server cluster, open PowerShell as an administrator and run the following command:
 
 ```powershell
 Install-AksHciAdAuth -name mynewcluster1 -keytab .\current.keytab -SPN k8s/[email protected] -adminUser contoso\bob

AKS-Hybrid/aks-arc-diagnostic-checker.md

@@ -22,14 +22,14 @@ It can be difficult to identify environment-related issues, such as networking c
 
 Before you begin, make sure you have the following prerequisites. If you don't meet the requirements for running the diagnostic checker tool, [file a support request](aks-troubleshoot.md#open-a-support-request):
 
-- Direct access to the Azure Stack HCI cluster where you created the AKS cluster. This access can be through remote desktop (RDP), or you can also sign in to one of the Azure Stack HCI physical nodes.
+- Direct access to the Azure Local cluster where you created the AKS cluster. This access can be through remote desktop (RDP), or you can also sign in to one of the Azure Local physical nodes.
 - Review the [networking concepts for creating an AKS cluster](aks-hci-network-system-requirements.md) and the [AKS cluster architecture](cluster-architecture.md).
 - The name of the logical network attached to the AKS cluster.
 - An SSH private key for the AKS cluster, used to sign in to the AKS cluster [control plane node](cluster-architecture.md#control-plane-nodes) VM.
 
 ## Obtain control plane node VM IP of the AKS cluster
 
-Run the following command from any one physical node in your Azure Stack HCI cluster. Ensure that you're passing the name, and not the Azure Resource Manager ID of the AKS cluster:
+Run the following command from any one physical node in your Azure Local cluster. Ensure that you're passing the name, and not the Azure Resource Manager ID of the AKS cluster:
 
 ```powershell
 invoke-command -computername (get-clusternode) -script {get-vmnetworkadapter -vmname *} | Where-Object {$_.Name -like "$cluster_name*control-plane-*"} | select vmname, ipaddresses
@@ -53,7 +53,7 @@ If you see a control plane VM, and it has:
 
 ## Run the diagnostic checker script
 
-Copy the following PowerShell script `run_diagnostic.ps1` into any one node of your Azure Stack HCI cluster:
+Copy the following PowerShell script `run_diagnostic.ps1` into any one node of your Azure Local cluster:
 
 ```powershell
 <#

AKS-Hybrid/aks-arc-use-node-taints.md

@@ -1,6 +1,6 @@
 ---
 title: Manage node taints for an AKS cluster
-description: Learn how to manage node taints in AKS on Azure Stack HCI 23H2
+description: Learn how to manage node taints in AKS on Azure Local, version 23H2
 ms.topic: how-to
 ms.custom:
 ms.date: 06/03/2024

AKS-Hybrid/aks-create-clusters-cli.md

@@ -1,6 +1,6 @@
 ---
 title: Create Kubernetes clusters using Azure CLI
-description: Learn how to create Kubernetes clusters in Azure Stack HCI using Azure CLI.
+description: Learn how to create Kubernetes clusters in Azure Local using Azure CLI.
 ms.topic: how-to
 ms.custom: devx-track-azurecli
 author: sethmanheim
@@ -14,20 +14,20 @@ ms.reviewer: guanghu
 
 [!INCLUDE [hci-applies-to-23h2](includes/hci-applies-to-23h2.md)]
 
-This article describes how to create Kubernetes clusters in Azure Stack HCI using Azure CLI. The workflow is as follows:
+This article describes how to create Kubernetes clusters in Azure Local using Azure CLI. The workflow is as follows:
 
-1. Create a Kubernetes cluster in Azure Stack HCI 23H2 using Azure CLI. The cluster is Azure Arc-connected by default.
+1. Create a Kubernetes cluster in Azure Local, version 23H2 using Azure CLI. The cluster is Azure Arc-connected by default.
 1. While creating the cluster, you provide a Microsoft Entra group that contains the list of Microsoft Entra users with Kubernetes cluster administrator access.
 1. Access the cluster using kubectl and your Microsoft Entra ID.
 1. Run a sample multi-container application with a web front end and a Redis instance in the cluster.
 
 ## Before you begin
 
 - Before you begin, make sure you have the following details from your on-premises infrastructure administrator:
-  - **Azure subscription ID** - The Azure subscription ID where Azure Stack HCI is used for deployment and registration.
-  - **Custom Location ID** - Azure Resource Manager ID of the custom location. The custom location is configured during the Azure Stack HCI cluster deployment. Your infrastructure admin should give you the Resource Manager ID of the custom location. This parameter is required in order to create Kubernetes clusters. You can also get the Resource Manager ID using `az customlocation show --name "<custom location name>" --resource-group <azure resource group> --query "id" -o tsv`, if the infrastructure admin provides a custom location name and resource group name.
-  - **Network ID** - Azure Resource Manager ID of the Azure Stack HCI logical network created following [these steps](aks-networks.md). Your admin should give you the ID of the logical network. This parameter is required in order to create Kubernetes clusters. You can also get the Azure Resource Manager ID using `az stack-hci-vm network lnet show --name "<lnet name>" --resource-group <azure resource group> --query "id" -o tsv` if you know the resource group in which the logical network was created.
-- You can run the steps in this article in a local development machine to create a Kubernetes cluster on your remote Azure Stack HCI deployment. Make sure you have the latest version of [Az CLI](/cli/azure/install-azure-cli) on your development machine. You can also choose to upgrade your Az CLI version using `az upgrade`.
+  - **Azure subscription ID** - The Azure subscription ID where Azure Local is used for deployment and registration.
+  - **Custom Location ID** - Azure Resource Manager ID of the custom location. The custom location is configured during the Azure Local cluster deployment. Your infrastructure admin should give you the Resource Manager ID of the custom location. This parameter is required in order to create Kubernetes clusters. You can also get the Resource Manager ID using `az customlocation show --name "<custom location name>" --resource-group <azure resource group> --query "id" -o tsv`, if the infrastructure admin provides a custom location name and resource group name.
+  - **Network ID** - Azure Resource Manager ID of the Azure Local logical network created following [these steps](aks-networks.md). Your admin should give you the ID of the logical network. This parameter is required in order to create Kubernetes clusters. You can also get the Azure Resource Manager ID using `az stack-hci-vm network lnet show --name "<lnet name>" --resource-group <azure resource group> --query "id" -o tsv` if you know the resource group in which the logical network was created.
+- You can run the steps in this article in a local development machine to create a Kubernetes cluster on your remote Azure Local deployment. Make sure you have the latest version of [Az CLI](/cli/azure/install-azure-cli) on your development machine. You can also choose to upgrade your Az CLI version using `az upgrade`.
 - To connect to the Kubernetes cluster from anywhere, create a Microsoft Entra group and add members to it. All the members in the Microsoft Entra group have cluster administrator access to the cluster. Make sure to add yourself as a member to the Microsoft Entra group. If you don't add yourself, you cannot access the Kubernetes cluster using kubectl. For more information about creating Microsoft Entra groups and adding users, see [Manage Microsoft Entra groups and group membership](/entra/fundamentals/how-to-manage-groups).
 - [Download and install kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) on your development machine. The Kubernetes command-line tool, kubectl, enables you to run commands against Kubernetes clusters. You can use kubectl to deploy applications, inspect and manage cluster resources, and view logs.
 

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

@@ -13,7 +13,7 @@ ms.lastreviewed: 01/30/2024
 
 [!INCLUDE [hci-applies-to-23h2](includes/hci-applies-to-23h2.md)]
 
-This article describes how to create Kubernetes clusters in Azure Stack HCI using the Azure portal. The workflow is as follows:
+This article describes how to create Kubernetes clusters in Azure Local using the Azure portal. The workflow is as follows:
 
 - How to create a Kubernetes cluster using the Azure portal. By default, the cluster is Azure Arc-connected.
 - While creating the cluster, you provide a Microsoft Entra group that contains the list of Microsoft Entra users with Kubernetes cluster administrator access.
@@ -81,5 +81,5 @@ This article describes how to create Kubernetes clusters in Azure Stack HCI usin
 
 ## Next steps
 
-- [Review AKS on Azure Stack HCI 23H2 prerequisites](aks-hci-network-system-requirements.md)
-- [What's new in AKS on Azure Stack HCI](aks-whats-new-23h2.md)
+- [Review AKS on Azure Local, version 23H2 prerequisites](aks-hci-network-system-requirements.md)
+- [What's new in AKS on Azure Local](aks-whats-new-23h2.md)

AKS-Hybrid/aks-create-containers.md

@@ -1,6 +1,6 @@
 ---
 title: Create Windows Server containers
-description: Learn how to create Windows Server containers in Azure Stack HCI.
+description: Learn how to create Windows Server containers in Azure Local.
 ms.topic: how-to
 author: sethmanheim
 ms.date: 07/15/2024

AKS-Hybrid/aks-hci-ip-address-planning.md

@@ -29,7 +29,7 @@ In the following scenario walk-through, you reserve IP addresses from a single n
 
 ### Example walkthrough for IP address reservation for Kubernetes clusters and applications
 
-Jane is an IT administrator just starting with AKS enabled by Azure Arc. Jane wants to deploy two Kubernetes clusters: Kubernetes cluster A and Kubernetes cluster B on the Azure Stack HCI cluster. Jane also wants to run a voting application on top of cluster A. This application has three instances of the front-end UI running across the two clusters and one instance of the backend database. All the AKS clusters and services are running in a single network, with a single subnet.
+Jane is an IT administrator just starting with AKS enabled by Azure Arc. Jane wants to deploy two Kubernetes clusters: Kubernetes cluster A and Kubernetes cluster B on the Azure Local cluster. Jane also wants to run a voting application on top of cluster A. This application has three instances of the front-end UI running across the two clusters and one instance of the backend database. All the AKS clusters and services are running in a single network, with a single subnet.
 
 - Kubernetes cluster A has 3 control plane nodes and 5 worker nodes.
 - Kubernetes cluster B has 1 control plane node and 3 worker nodes.
@@ -48,17 +48,17 @@ Continuing with this example, and adding it to the following table, you get:
 
 | Parameter    | Number of IP addresses | How and where to make this reservation |
 |------------------|---------|---------------|
-| AKS Arc VMs and K8s version upgrade  | Reserve 14 IP addresses | Make this reservation through IP pools in the Azure Stack HCI logical network. |
+| AKS Arc VMs and K8s version upgrade  | Reserve 14 IP addresses | Make this reservation through IP pools in the Azure Local logical network. |
 | Control plane IP | Reserve 2 IP addresses, one for AKS Arc cluster | Use the `controlPlaneIP` parameter to pass the IP address for control plane IP. Ensure that this IP is in the same subnet as the Arc logical network, but outside the IP pool defined in the Arc logical network. |
 | Load balancer IPs | 3 IP address for Kubernetes services, for Jane's voting application. | These IP addresses are used when you install a load balancer on cluster A. You can use the MetalLB Arc extension, or bring your own 3rd party load balancer. Ensure that this IP is in the same subnet as the Arc logical network, but outside the IP pool defined in the Arc VM logical network. |
 
 ### LNETs considerations for AKS clusters and Arc VMs
 
-Logical networks on Azure Stack HCI are used by both AKS clusters and Arc VMs. You can configure logical networks in one of the following 2 ways:
+Logical networks on Azure Local are used by both AKS clusters and Arc VMs. You can configure logical networks in one of the following 2 ways:
 - Share a logical network between AKS and Arc VMs.
 - Define separate logical networks for AKS clusters and Arc VMs.
 
-Sharing a logical network between AKS and Arc VMs on Azure Stack HCI offers the benefit of streamlined communication, cost savings, and simplified network management. However, this approach also introduces potential challenges such as resource contention, security risks, and complexity in troubleshooting.
+Sharing a logical network between AKS and Arc VMs on Azure Local offers the benefit of streamlined communication, cost savings, and simplified network management. However, this approach also introduces potential challenges such as resource contention, security risks, and complexity in troubleshooting.
 
 | **Criteria**                              | **Sharing a logical network**                                  | **Defining separate logical networks**     |
 |-------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------|
@@ -88,4 +88,4 @@ AKS provides a **default value of 10.96.0.0/12** for the service network CIDR. A
 
 ## Next steps
 
-[Create logical networks for Kubernetes clusters on Azure Stack HCI 23H2](aks-networks.md)
+[Create logical networks for Kubernetes clusters on Azure Local, version 23H2](aks-networks.md)