You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AKS-Arc/kubernetes-walkthrough-powershell.md
+23-24Lines changed: 23 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,31 +1,30 @@
1
1
---
2
-
title: Use PowerShell to set up Kubernetes on Azure Local and Windows Server clusters
2
+
title: Use PowerShell to set up Kubernetes on Windows Server clusters
3
3
description: Learn how to set up an AKS host and create Kubernetes clusters using Windows PowerShell.
4
4
author: sethmanheim
5
5
ms.topic: quickstart
6
-
ms.date: 02/21/2025
6
+
ms.date: 03/28/2025
7
7
ms.author: sethm
8
8
ms.lastreviewed: 05/02/2022
9
-
ms.reviewer: mikek
9
+
ms.reviewer: abha
10
10
ms.custom:
11
11
- mode-api
12
12
- kr2b-contr-experiment
13
13
- devx-track-azurepowershell
14
14
15
-
# Intent: As an IT Pro, I want to use Windows PowerShell to create an AKS on Azure Local and Windows Server cluster.
16
-
# Keyword: AKS setup PowerShell
15
+
# Intent: As an IT Pro, I want to use Windows PowerShell to create an AKS on Windows Server cluster.
16
+
# Keyword: AKS set up PowerShell
17
17
---
18
18
19
-
# Set up an Azure Kubernetes Service host on Azure Local and Windows Server and deploy a workload cluster using PowerShell
19
+
# Set up an Azure Kubernetes Service host on Windows Server and deploy a workload cluster using PowerShell
20
20
21
-
> Applies to: Azure Local or Windows Server Datacenter
21
+
> Applies to: Windows Server Datacenter
22
22
23
-
This quickstart guides you through setting up an Azure Kubernetes Service (AKS) host. You create Kubernetes clusters on Azure Local and Windows Server using PowerShell. To use Windows Admin Center instead, see [Set up with Windows Admin Center](setup.md).
23
+
This quickstart guides you through setting up an Azure Kubernetes Service (AKS) host. You create Kubernetes clusters on Windows Server using PowerShell. To use Windows Admin Center instead, see [Set up with Windows Admin Center](setup.md).
24
24
25
25
> [!NOTE]
26
-
> - If you have pre-staged cluster service objects and DNS records, see [Deploy an AKS host with prestaged cluster service objects and DNS records using PowerShell](prestage-cluster-service-host-create.md).
26
+
> - If you pre-staged cluster service objects and DNS records, see [Deploy an AKS host with prestaged cluster service objects and DNS records using PowerShell](prestage-cluster-service-host-create.md).
27
27
> - If you have a proxy server, see [Set up an AKS host and deploy a workload cluster using PowerShell and a proxy server](set-proxy-settings.md).
28
-
> - Installing AKS on Azure Local after setting up Arc VMs is not supported. For more information, see [known issues with Arc VMs](/azure/azure-local/manage/troubleshoot-arc-enabled-vms#limitations-and-known-issues). If you want to install AKS on Azure Local, you must uninstall Arc Resource Bridge and then install AKS on Azure Local. You can deploy a new Arc Resource Bridge again after you clean up and install AKS, but it won't remember the VM entities you created previously.
Run checks on every physical node to see if all the requirements to install AKS enabled by Arc are satisfied. Open PowerShell as an administrator and run the following [Initialize-AksHciNode](./reference/ps/initialize-akshcinode.md) command on all nodes in your Azure Local and Windows Server cluster:
72
+
Run checks on every physical node to see if all the requirements to install AKS enabled by Arc are satisfied. Open PowerShell as an administrator and run the following [Initialize-AksHciNode](./reference/ps/initialize-akshcinode.md) command on all nodes in your Windows Server cluster:
74
73
75
74
```powershell
76
75
Initialize-AksHciNode
77
76
```
78
77
79
-
## Step 2: Create a virtual network
78
+
## Step 2: create a virtual network
80
79
81
-
Run the following commands on any one node in your Azure Local and Windows Server cluster.
80
+
Run the following commands on any one node in your Windows Server cluster.
82
81
83
82
To get the names of your available switches, run the following command. Make sure the `SwitchType` of your VM switch is **External**:
> You must customize the values shown in this example command for your environment.
106
105
107
-
## Step 3: Configure your deployment
106
+
## Step 3: configure your deployment
108
107
109
-
Run the following commands on any node in your Azure Local and Windows Server cluster.
108
+
Run the following commands on any node in your Windows Server cluster.
110
109
111
110
To create the configuration settings for the AKS host, use the [Set-AksHciConfig](./reference/ps/set-akshciconfig.md) command. You must specify the `imageDir`, `workingDir`, and `cloudConfigLocation` parameters. If you want to reset your configuration details, run the command again with new parameters.
### Option 1: Use your Microsoft Entra account if you have "Owner" permissions
126
+
### Option 1: use your Microsoft Entra account if you have "Owner" permissions
128
127
129
128
Run the following [Set-AksHciRegistration](/azure-stack/aks-hci/reference/ps/set-akshciregistration) PowerShell command with your subscription and resource group name to sign in to Azure. You must have an Azure subscription, and an existing Azure resource group in the Australia East, East US, Southeast Asia, or West Europe Azure regions:
If you don't have access to a subscription on which you're an **Owner**, you can register your AKS host to Azure for billing using a service principal. For more information about how to use a service principal, see [register AKS on Azure Local and Windows Server using a service principal](reference/ps/set-akshciregistration.md#register-aks-hybrid-using-a-service-principal).
138
137
139
-
## Step 5: Start a new deployment
138
+
## Step 5: start a new deployment
140
139
141
-
Run the following command on any node in your Azure Local or Windows Server cluster.
140
+
Run the following command on any node in your Windows Server cluster.
142
141
143
142
After you configure your deployment, you must start it in order to install the AKS agents and services, and the AKS host. To begin deployment, run the following command:
144
143
@@ -152,7 +151,7 @@ Install-AksHci
152
151
> [!WARNING]
153
152
> During installation of your AKS host, a **Kubernetes - Azure Arc** resource type is created in the resource group that's set during registration. Do not delete this resource, as it represents your AKS host. You can identify the resource by checking its distribution field for a value of `aks_management`. If you delete this resource, it results in an out-of-policy deployment.
154
153
155
-
## Step 6: Create a Kubernetes cluster
154
+
## Step 6: create a Kubernetes cluster
156
155
157
156
After you install your AKS host, you can deploy a Kubernetes cluster. Open PowerShell as an administrator and run the following [New-AksHciCluster](./reference/ps/new-akshcicluster.md) command. This example command creates a new Kubernetes cluster with one Linux node pool named `linuxnodepool` with a node count of 1.
158
157
@@ -196,7 +195,7 @@ VmSize : Standard_K8S3_v1
196
195
Phase : Deployed
197
196
```
198
197
199
-
## Step 7: Connect your cluster to Arc-enabled Kubernetes
198
+
## Step 7: connect your cluster to Arc-enabled Kubernetes
200
199
201
200
Connect your cluster to Arc-enabled Kubernetes by running the [Enable-AksHciArcConnection](./reference/ps/enable-akshciarcconnection.md) command. The following example connects your Kubernetes cluster to Arc using the subscription and resource group details you passed in the `Set-AksHciRegistration` command:
> In previous versions of AKS on Azure Local and Windows Server, the [Set-AksHciCluster](/azure-stack/aks-hci/reference/ps/set-akshcicluster) command was also used to scale worker nodes. Now that AKS is introducing node pools in workload clusters, you can only use this command to scale worker nodes if your cluster was created with the old parameter set in [New-AksHciCluster](/azure-stack/aks-hci/reference/ps/new-akshcicluster).
227
+
> In previous versions of AKS on Windows Server, the [Set-AksHciCluster](/azure-stack/aks-hci/reference/ps/set-akshcicluster) command was also used to scale worker nodes. Now that AKS is introducing node pools in workload clusters, you can only use this command to scale worker nodes if your cluster was created with the old parameter set in [New-AksHciCluster](/azure-stack/aks-hci/reference/ps/new-akshcicluster).
229
228
230
229
To scale worker nodes in a node pool, use the [Set-AksHciNodePool](/azure-stack/aks-hci/reference/ps/set-akshcinodepool) command.
Copy file name to clipboardExpand all lines: AKS-Arc/setup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Quickstart to set up AKS enabled by Azure Arc using Windows Admin Center
3
3
description: Learn how to set up AKS enabled by Azure Arc using Windows Admin Center
4
4
author: sethmanheim
5
5
ms.topic: quickstart
6
-
ms.date: 12/27/2023
6
+
ms.date: 03/28/2025
7
7
ms.author: sethm
8
8
ms.lastreviewed: 03/16/2022
9
9
ms.reviewer: dawhite
@@ -77,7 +77,7 @@ Now that you verified the system settings, follow these steps:
77
77
78
78
[](.\media\setup\host-configuration-static.png#lightbox)
79
79
80
-
(Optional) Configure proxy settings as required for the AKS host. These settings are dependent on the proxy settings that are provisioned on the Azure Local host machine. Make sure you also provision the list of IP addresses that needs to bypass the proxy. When complete, select **Next: Review + Create**.
80
+
(Optional) Configure proxy settings as required for the AKS host. Make sure you also provision the list of IP addresses that needs to bypass the proxy. When complete, select **Next: Review + Create**.
81
81
82
82
[](.\media\setup\proxy-settings-host-configuration.png#lightbox)
0 commit comments