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: articles/aks/ssh.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,15 @@ ms.author: iainfou
12
12
13
13
# SSH to Azure Kubernetes Service (AKS) cluster nodes
14
14
15
-
Throughout the lifecycle of your Azure Kubernetes Service (AKS) cluster, you may need to access an AKS node. This access could be for maintenance, log collection, or other troubleshooting operations. The AKS nodes are Linux VMs, so you can access them using SSH. For security purposes, the AKS nodes are not exposed to the internet. This article shows you how to create an SSH connection with an AKS node using their private IP addresses.
15
+
Throughout the lifecycle of your Azure Kubernetes Service (AKS) cluster, you may need to access an AKS node. This access could be for maintenance, log collection, or other troubleshooting operations. The AKS nodes are Linux VMs, so you can access them using SSH. For security purposes, the AKS nodes are not exposed to the internet.
16
+
17
+
This article shows you how to create an SSH connection with an AKS node using their private IP addresses.
16
18
17
19
## Add your public SSH key
18
20
19
-
By default, SSH keys are generated for you when you create an AKS cluster. If you did not specify your own SSH keys when you created your AKS cluster, you first need to add your public SSH keys to the AKS nodes. To add your SSH key to an AKS node, complete the following steps:
21
+
By default, SSH keys are generated when you create an AKS cluster. If you did not specify your own SSH keys when you created your AKS cluster, add your public SSH keys to the AKS nodes.
22
+
23
+
To add your SSH key to an AKS node, complete the following steps:
20
24
21
25
1. Get the resource group name for your AKS cluster resources using [az aks show][az-aks-show]. Provide your own core resource group and AKS cluster name:
22
26
@@ -50,15 +54,15 @@ By default, SSH keys are generated for you when you create an AKS cluster. If yo
50
54
51
55
## Get the AKS node address
52
56
53
-
The AKS nodes are not publicly exposed to the internet. To SSH to the AKS nodes, you use their internal, private IP addresses.
57
+
The AKS nodes are not publicly exposed to the internet. To SSH to the AKS nodes, you use the private IP address.
54
58
55
59
View the private IP address of an AKS cluster node using the [az vm list-ip-addresses][az-vm-list-ip-addresses] command. Provide your own AKS cluster resource group name obtained in a previous [az-aks-show][az-aks-show] step:
56
60
57
61
```azurecli
58
62
az vm list-ip-addresses --resource-group MC_myAKSCluster_myAKSCluster_eastus -o table
59
63
```
60
64
61
-
The following example output shows the private IP addresses the AKS nodes:
65
+
The following example output shows the private IP addresses of the AKS nodes:
62
66
63
67
```
64
68
VirtualMachine PrivateIPAddresses
@@ -82,7 +86,7 @@ To create an SSH connection to an AKS node, you run a helper pod in your AKS clu
1. In a new terminal window, list the pods on your AKS cluster using the [kubectl get pods][kubectl-get] command. The pod created in the previous step starts with the name *aks-ssh*, as shown in the following example:
89
+
1. In a new terminal window, not connected to your container, list the pods on your AKS cluster using the [kubectl get pods][kubectl-get] command. The pod created in the previous step starts with the name *aks-ssh*, as shown in the following example:
0 commit comments