Skip to content

Commit 2c99276

Browse files
committed
[AKS] Additional minor edits
1 parent 31c3330 commit 2c99276

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

articles/aks/ssh.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,15 @@ ms.author: iainfou
1212

1313
# SSH to Azure Kubernetes Service (AKS) cluster nodes
1414

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.
1618

1719
## Add your public SSH key
1820

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:
2024

2125
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:
2226

@@ -50,15 +54,15 @@ By default, SSH keys are generated for you when you create an AKS cluster. If yo
5054
5155
## Get the AKS node address
5256
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.
5458
5559
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:
5660
5761
```azurecli
5862
az vm list-ip-addresses --resource-group MC_myAKSCluster_myAKSCluster_eastus -o table
5963
```
6064

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:
6266

6367
```
6468
VirtualMachine PrivateIPAddresses
@@ -82,7 +86,7 @@ To create an SSH connection to an AKS node, you run a helper pod in your AKS clu
8286
apt-get update && apt-get install openssh-client -y
8387
```
8488

85-
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:
8690

8791
```
8892
$ kubectl get pods

0 commit comments

Comments
 (0)