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/node-access.md
+11-12Lines changed: 11 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,9 @@ ms.custom: contperf-fy21q4
12
12
13
13
# Connect to Azure Kubernetes Service (AKS) cluster nodes for maintenance or troubleshooting
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. You can access AKS nodes using SSH, including Windows Server nodes. You can also [connect to Windows Server nodes using remote desktop protocol (RDP) connections][aks-windows-rdp]. For security purposes, the AKS nodes aren't exposed to the internet. To connect to the AKS nodes, you use `kubectl debug` or the private IP address.
15
+
Throughout the lifecycle of your Azure Kubernetes Service (AKS) cluster, you might need to access an AKS node. This access could be for maintenance, log collection, or troubleshooting operations. You can securely authenticate against AKS Linux and Windows nodes using SSH, and you can also [connect to Windows Server nodes using remote desktop protocol (RDP)][aks-windows-rdp]. For security reasons, the AKS nodes aren't exposed to the internet. To connect to the AKS nodes, you use `kubectl debug` or the private IP address.
16
16
17
-
What's more, AKS now supports [updating SSH key on all existing nodepools][updating SSH key]
18
-
19
-
This article shows you how to create a connection to an AKS node and update SSH key on existing AKS cluster.
17
+
This article shows you how to create a connection to an AKS node and update the SSH key on an existing AKS cluster.
20
18
21
19
## Before you begin
22
20
@@ -165,35 +163,35 @@ When done, `exit` the SSH session, stop any port forwarding, and then `exit` the
165
163
kubectl delete pod node-debugger-aks-nodepool1-12345678-vmss000000-bkmmx
166
164
```
167
165
168
-
## Update the SSH key on existing AKS cluster (public preview)
166
+
## Update SSH key on an existing AKS cluster (preview)
169
167
170
168
### Prerequisites
171
169
*[Azure CLI][install-azure-cli] and the `aks-preview` 0.5.111 or later CLI extension installed.
172
170
173
171
### Limitation
174
172
* Updating SSH key is supported for VMSS AKS clusters.
175
173
176
-
Use `az aks update`to update new SSH key on AKS cluster. Note that the SSH key of all nodepools will be updated.
174
+
Use the [az aks update][az-aks-update] command to update the SSH key on the cluster. This operation will update the key on all node pools. You can either specify the key or a key file using the `--ssh-key-value` argument.
177
175
178
176
```azurecli
179
-
az aks update --name myAKSCluster --resource-group MyResourceGroup --ssh-key-value <new SSH key value>
177
+
az aks update --name myAKSCluster --resource-group MyResourceGroup --ssh-key-value <new SSH key value or SSH key file>
180
178
```
181
179
182
-
Example:
183
-
You can attach the new SSH key value directly to`--ssh-key-value`.
180
+
Examples:
181
+
In the following example, you can specify the new SSH key value for the`--ssh-key-value` argument.
184
182
185
183
```azurecli
186
184
az aks update --name myAKSCluster --resource-group MyResourceGroup --ssh-key-value 'ssh-rsa AAAAB3Nza-xxx'
187
185
```
188
186
189
-
Attaching SSH key file is also supported.
187
+
In the following example, you specify a SSH key file.
190
188
191
189
```azurecli
192
190
az aks update --name myAKSCluster --resource-group MyResourceGroup --ssh-key-value .ssh/id_rsa.pub
193
191
```
194
192
195
193
> [!IMPORTANT]
196
-
> During this operation, all VMSS instances will be upgraded and re-imaged to fit the new SSH key.
194
+
> During this operation, all virtual machine scale set instances are upgraded and re-imaged to use the new SSH key.
197
195
198
196
## Next steps
199
197
@@ -207,5 +205,6 @@ If you need more troubleshooting data, you can [view the kubelet logs][view-kube
0 commit comments