Skip to content

Commit e2e2c0f

Browse files
Merge pull request #236057 from mattmcinnes/patch-80
[Doc-a-thon] Updating node-access.md
2 parents 5ca5243 + de4819f commit e2e2c0f

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

articles/aks/node-access.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22
title: Connect to Azure Kubernetes Service (AKS) cluster nodes
33
description: Learn how to connect to Azure Kubernetes Service (AKS) cluster nodes for troubleshooting and maintenance tasks.
44
ms.topic: article
5-
ms.date: 11/3/2022
5+
ms.date: 04/26/2023
6+
ms.reviewer: mattmcinnes
67
ms.custom: contperf-fy21q4
78

89
#Customer intent: As a cluster operator, I want to learn how to connect to virtual machines in an AKS cluster to perform maintenance or troubleshoot a problem.
@@ -16,7 +17,7 @@ This article shows you how to create a connection to an AKS node and update the
1617

1718
## Before you begin
1819

19-
This article assumes you have an SSH key. If not, you can create an SSH key using [macOS or Linux][ssh-nix] or [Windows][ssh-windows]. Make sure you save the key pair in an OpenSSH format, other formats like .ppk are not supported.
20+
This article assumes you have an SSH key. If not, you can create an SSH key using [macOS or Linux][ssh-nix] or [Windows][ssh-windows]. Make sure you save the key pair in an OpenSSH format, other formats like .ppk aren't supported.
2021

2122
You also need the Azure CLI version 2.0.64 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
2223

@@ -74,7 +75,7 @@ To create the SSH connection to the Windows Server node from another node, use t
7475

7576
> [!IMPORTANT]
7677
>
77-
> The following steps for creating the SSH connection to the Windows Server node from another node can only be used if you created your AKS cluster using the Azure CLI and the `--generate-ssh-keys` parameter. If you didn't use this method to create your cluster, you'll use a password instead of an SSH key. To do this, see [Create the SSH connection to a Windows node using a password](#create-the-ssh-connection-to-a-windows-node-using-a-password)
78+
> The following steps for creating the SSH connection to the Windows Server node from another node can only be used if you created your AKS cluster using the Azure CLI and the `--generate-ssh-keys` parameter. If you didn't use this method to create your cluster, use a password instead of an SSH key. To do this, see [Create the SSH connection to a Windows node using a password](#create-the-ssh-connection-to-a-windows-node-using-a-password)
7879
7980
Open a new terminal window and use the `kubectl get pods` command to get the name of the pod started by `kubectl debug`.
8081

@@ -123,7 +124,7 @@ aksnpwin000000 Ready agent 87s v1.19.9 10.240.0.
123124

124125
In the above example, *10.240.0.67* is the internal IP address of the Windows Server node.
125126

126-
Create an SSH connection to the Windows Server node using the internal IP address, and connect to port 22 through port 2022 on your development computer. The default username for AKS nodes is *azureuser*. Accept the prompt to continue with the connection. You are then provided with the bash prompt of your Windows Server node:
127+
Create an SSH connection to the Windows Server node using the internal IP address, and connect to port 22 through port 2022 on your development computer. The default username for AKS nodes is *azureuser*. Accept the prompt to continue with the connection. You're then provided with the bash prompt of your Windows Server node:
127128

128129
```bash
129130
ssh -o 'ProxyCommand ssh -p 2022 -W %h:%p [email protected]' [email protected]
@@ -217,7 +218,7 @@ kubectl delete pod node-debugger-aks-nodepool1-12345678-vmss000000-bkmmx
217218
> [!NOTE]
218219
> Updating of the SSH key is supported on Azure virtual machine scale sets with AKS clusters.
219220
220-
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.
221+
Use the [az aks update][az-aks-update] command to update the SSH key on the cluster. This operation updates the key on all node pools. You can either specify the key or a key file using the `--ssh-key-value` argument.
221222

222223
```azurecli
223224
az aks update --name myAKSCluster --resource-group MyResourceGroup --ssh-key-value <new SSH key value or SSH key file>

0 commit comments

Comments
 (0)