Skip to content

Commit 4fa3d47

Browse files
authored
Update ssh-connect-to-windows-and-linux-worker-nodes.md
split windows and linux commands
1 parent 8ace7ee commit 4fa3d47

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

AKS-Arc/ssh-connect-to-windows-and-linux-worker-nodes.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,14 +31,19 @@ This article explains how to use SSH to connect to both Windows and Linux nodes.
3131
kubectl --kubeconfig /path/to/aks-cluster-kubeconfig get nodes -o wide |
3232
```
3333

34-
1. Run `ssh cloud@<IP address of the node>` to connect to a worker node:
34+
1. Run `ssh` to connect to a worker node:
3535

3636
> [!NOTE]
3737
> You must pass the correct location to your SSH private key. The following example uses the default location of **~/.ssh/id_rsa**, but you might need to change this location if you requested a different path. To change the location, see [Configure SSH keys](configure-ssh-keys.md) to specify the `--ssh-key-value` parameter when you create an AKS Arc cluster.
3838
39+
For Linux worker node, run the following
3940
```azurecli
4041
ssh -i $env:USERPROFILE\.ssh\id_rsa clouduser@<IP address of the node>
4142
```
43+
For Windows worker node, run the following
44+
```azurecli
45+
ssh -i $env:USERPROFILE\.ssh\id_rsa Administrator@<IP address of the node>
46+
```
4247

4348
If you encounter SSH login issues, verify that your IP address is included in the **--ssh-auth-ip list**. To check this list, run `az aksarc show --name "$<aks_cluster_name>" --resource-group "$<resource_group_name>"` and look for `authorizedIpRanges` under `clusterVmAccessProfile`.
4449

0 commit comments

Comments
 (0)