Merge pull request #16226 from v-thepet/aks-hci2

[bulk] Azure Stack HCI to Azure Local rebrand in AKS-Hybrid (k-w, includes, ref)

Author: Jill Grant

AKS-Hybrid/TOC.yml

@@ -11,10 +11,10 @@
     href: supported-kubernetes-versions.md  
   - name: Data collection
     href: data-collection.md
-- name: AKS on Azure Stack HCI 23H2
+- name: AKS on Azure Local, version 23H2
   expanded: true
   items:
-  - name: What's new in AKS on Azure Stack HCI 23H2
+  - name: What's new in AKS on Azure Local, version 23H2
     href: aks-whats-new-23h2.md
   - name: Concepts
     items:
@@ -152,7 +152,7 @@
       href: /rest/api/hybridcontainer/operation-groups
   - name: Resources
     items:
-    - name: Azure Stack HCI
+    - name: Azure Local
       href: /azure-stack/hci/index
     - name: Azure hybrid cloud
       href: /hybrid
@@ -355,7 +355,7 @@
           href: create-replicasets.md
         - name: Create a StatefulSet
           href: create-statefulset.md
-    - name: Availability with 2-node HCI cluster
+    - name: Availability with 2-node Azure Local cluster
       href: deploy-cluster-on-two-node-hci.md
     - name: Security
       items:
@@ -557,11 +557,11 @@
       href: known-issues-uninstall.yml
     - name: Other
       href: known-issues.yml
-    - name: Azure Stack HCI issues
+    - name: Azure Local issues
       items:
-      - name: Cluster validation reporting in Azure Stack HCI
+      - name: Cluster validation reporting in Azure Local
         href: /azure-stack/hci/manage/validate-qos
-      - name: CredSSP in Azure Stack HCI
+      - name: CredSSP in Azure Local
         href: /azure-stack/hci/manage/troubleshoot-credssp
     - name: Support policies
       href: support-policies.md

AKS-Hybrid/create-kubernetes-cluster.md

@@ -39,7 +39,7 @@ This section describes how to use the Create Kubernetes cluster wizard through t
 
     :::image type="content" source="media/create-kubernetes-cluster/basics.png" alt-text="Screenshot showing Basics cluster creation pane." lightbox="media/create-kubernetes-cluster/basics.png":::
 
-1. This step is mandatory. Configure node pools to run your workloads on the **Node pools** page. You can add any number of Windows node pools and Linux node pools. If you enabled Azure Arc integration earlier in this wizard, configure a Linux node pool with at least one Linux worker node. However, if you disabled Azure Arc integration earlier, then any node pool addition allows you to proceed to the next step. You can also set maximum pod counts and node taints when configuring node pools. Both of these settings are optional. For more information about the available taint settings, see [New-AksHciCluster](./reference/ps/new-akshcicluster.md#new-aks-hci-cluster-with-a-linux-node-pool-and-taints).
+1. This step is mandatory. Configure node pools to run your workloads on the **Node pools** page. You can add any number of Windows node pools and Linux node pools. If you enabled Azure Arc integration earlier in this wizard, configure a Linux node pool with at least one Linux worker node. However, if you disabled Azure Arc integration earlier, then any node pool addition allows you to proceed to the next step. You can also set maximum pod counts and node taints when configuring node pools. Both of these settings are optional. For more information about the available taint settings, see [New-AksHciCluster](./reference/ps/new-akshcicluster.md#new-aks-on-azure-local-cluster-with-a-linux-node-pool-and-taints).
 
    ![Screenshot that illustrates the Node pools page of the Kubernetes cluster wizard where you can configure maximum pod counts and taints.](./media/create-kubernetes-cluster/node-pool-added.png)
 

AKS-Hybrid/includes/data-allow-table.md

@@ -13,15 +13,15 @@ ms.lastreviewed: 08/15/2022
 
 |  URL | Port | Notes |
 |  :---| :---| :---|
-|  msk8s.api.cdp.microsoft.com | 443  | Used when downloading the AKS on Azure Stack HCI product catalog, product bits, and OS images from SFS. Occurs when running `Set-AksHciConfig` and any time you download from SFS. |
-|  msk8s.b.tlu.dl.delivery.mp.microsoft.com </br> msk8s.f.tlu.dl.delivery.mp.microsoft.com | 80 | Used when downloading the AKS on Azure Stack HCI product catalog, product bits, and OS images from SFS. Occurs when running `Set-AksHciConfig` and any time you download from SFS. |
+|  msk8s.api.cdp.microsoft.com | 443  | Used when downloading the AKS on Azure Local product catalog, product bits, and OS images from SFS. Occurs when running `Set-AksHciConfig` and any time you download from SFS. |
+|  msk8s.b.tlu.dl.delivery.mp.microsoft.com </br> msk8s.f.tlu.dl.delivery.mp.microsoft.com | 80 | Used when downloading the AKS on Azure Local product catalog, product bits, and OS images from SFS. Occurs when running `Set-AksHciConfig` and any time you download from SFS. |
 |  login.microsoftonline.com </br> login.windows.net </br> management.azure.com </br> msft.sts.microsoft.com </br> graph.windows.net | 443 | Used for logging into Azure when running `Set-AksHciRegistration`. |
 |  ecpacr.azurecr.io </br> mcr.microsoft.com </br> \*.mcr.microsoft.com </br> \*.data.mcr.microsoft.com </br> \*.blob.core.windows.net </br> US endpoint: wus2replica\*.blob.core.windows.net | 443 | Required to pull container images when running `Install-AksHci`. |
 |  \<region>.dp.kubernetesconfiguration.azure.com | 443  | Required to onboard AKS hybrid clusters to Azure Arc. |
 | gbl.his.arc.azure.com | 443 | Required to get the regional endpoint for pulling system-assigned Managed Identity certificates. |
 | \*.his.arc.azure.com | 443 | Required to pull system-assigned Managed Identity certificates. |
-| k8connecthelm.azureedge.net	| 443 | Arc-enabled Kubernetes uses Helm 3 to deploy Azure Arc agents on the AKS-HCI management cluster. This endpoint is needed for the Helm client download to facilitate deployment of the agent helm chart.
+| k8connecthelm.azureedge.net	| 443 | Arc-enabled Kubernetes uses Helm 3 to deploy Azure Arc agents on the AKS on Azure Local management cluster. This endpoint is needed for the Helm client download to facilitate deployment of the agent helm chart.
 | \*.arc.azure.net| 443 | Required to manage AKS hybrid clusters in Azure portal. |
 | dl.k8s.io | 443 | Required to download and update Kubernetes binaries for Azure Arc. |
-|  akshci.azurefd.net | 443 | Required for AKS on Azure Stack HCI billing when running `Install-AksHci`. |
-|  v20.events.data.microsoft.com </br> gcs.prod.monitoring.core.windows.net | 443 | Used periodically to send Microsoft required diagnostic data from the Azure Stack HCI or Windows Server host. |
+|  akshci.azurefd.net | 443 | Required for AKS on Azure Local billing when running `Install-AksHci`. |
+|  v20.events.data.microsoft.com </br> gcs.prod.monitoring.core.windows.net | 443 | Used periodically to send Microsoft required diagnostic data from the Azure Local or Windows Server host. |

AKS-Hybrid/includes/hci-applies-to-23h2.md

@@ -8,4 +8,4 @@ ms.reviewer: alkohli
 ms.lastreviewed: 10/13/2023
 ---
 
-> Applies to: Azure Stack HCI, version 23H2
+> Applies to: Azure Local, version 23H2

AKS-Hybrid/includes/install-akshci-ps.md

@@ -9,12 +9,12 @@ ms.lastreviewed: 05/02/2022
 
 ---
 
-Follow these steps on all nodes in your Azure Stack HCI cluster or Windows Server cluster:
+Follow these steps on all nodes in your Azure Local cluster or Windows Server cluster:
 
 > [!NOTE]
 > If you are using remote PowerShell, you must use CredSSP.
 
-1. Close all open PowerShell windows, open a new PowerShell session as administrator, and run the following command on all nodes in your Azure Stack HCI or Windows Server cluster:
+1. Close all open PowerShell windows, open a new PowerShell session as administrator, and run the following command on all nodes in your Azure Local or Windows Server cluster:
 
    ```powershell  
    Install-PackageProvider -Name NuGet -Force 
@@ -23,7 +23,7 @@ Follow these steps on all nodes in your Azure Stack HCI cluster or Windows Serve
 
    You must close all existing PowerShell windows again to ensure that loaded modules are refreshed. Don't continue to the next step until you close all open PowerShell windows.
 
-1. Install the AKS-HCI PowerShell module by running the following command on all nodes in your Azure Stack HCI or Windows Server cluster:
+1. Install the AKS-HCI PowerShell module by running the following command on all nodes in your Azure Local or Windows Server cluster:
 
    ```powershell
    Install-Module -Name AksHci -Repository PSGallery -Force -AcceptLicense

AKS-Hybrid/known-issues-arc.yml

@@ -10,7 +10,7 @@ metadata:
 
 title: Resolve errors when enabling or disabling Azure Arc on your AKS workload clusters in AKS enabled by Arc
 summary: |
-  Applies to: AKS on Azure Stack HCI, AKS on Windows Server
+  Applies to: AKS on Azure Local, AKS on Windows Server
   
   This article describes errors you might encounter (and their workarounds) while connecting or disconnecting your AKS workload clusters to Azure Arc using the PowerShell cmdlets [`Enable-AksHciArcConnection`](./reference/ps/enable-akshciarcconnection.md) and [`Disable-AksHciArcConnection`](./reference/ps/disable-akshciarcconnection.md) in AKS Arc. For issues that are not covered in this article, see [Troubleshooting Arc enabled Kubernetes](/azure/azure-arc/kubernetes/troubleshooting).
   
@@ -57,10 +57,10 @@ sections:
         answer: | 
           This error usually points to one of the following issues:
           
-          - The clusters were created in an Azure VM in a virtualized environment, or you deployed AKS on Azure Stack HCI on multiple levels of virtualization. 
+          - The clusters were created in an Azure VM in a virtualized environment, or you deployed AKS on Azure Local on multiple levels of virtualization. 
           - A slow internet caused the timeout.
           
-          If one of the above scenarios applies to you, run [Disable-AksHciArcConnection](./reference/ps/disable-akshciarcconnection.md), and try connecting again. If the above scenario doesn't apply to you, [open a support issue](./help-support.md) for AKS on Azure Stack HCI.
+          If one of the above scenarios applies to you, run [Disable-AksHciArcConnection](./reference/ps/disable-akshciarcconnection.md), and try connecting again. If the above scenario doesn't apply to you, [open a support issue](./help-support.md) for AKS on Azure Local.
       - question: | 
           Error: "Secrets "sh.helm.release.v1.azure-arc.v1" not found"
 
@@ -90,7 +90,7 @@ sections:
 
         answer: | 
           This error usually means that you already connected your AKS cluster to Arc-enabled Kubernetes.
-          To confirm it's connected, go to the [Azure portal](https://portal.azure.com) and check under the subscription and resource group you provided when you ran [`Set-AksHciRegistration`](./reference/ps/set-akshciregistration.md) (if you used default values) or [`Enable-AksHciArcConnection`](./reference/ps/enable-akshciarcconnection.md) (if you didn't use default values). You can also confirm if your AKS on Azure Stack HCI cluster is connected to Azure by running the [`az connectedk8s show` ](/cli/azure/connectedk8s#az-connectedk8s-show) Azure CLI command. If you don't see your workload cluster, run `Disable-AksHciArcConnection` and try again.
+          To confirm it's connected, go to the [Azure portal](https://portal.azure.com) and check under the subscription and resource group you provided when you ran [`Set-AksHciRegistration`](./reference/ps/set-akshciregistration.md) (if you used default values) or [`Enable-AksHciArcConnection`](./reference/ps/enable-akshciarcconnection.md) (if you didn't use default values). You can also confirm if your AKS on Azure Local cluster is connected to Azure by running the [`az connectedk8s show` ](/cli/azure/connectedk8s#az-connectedk8s-show) Azure CLI command. If you don't see your workload cluster, run `Disable-AksHciArcConnection` and try again.
           
           
       - question: |