Skip to content

Commit 4febac7

Browse files
authored
Update rdp.md
1 parent a82fa1b commit 4febac7

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/aks/rdp.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 04/26/2023
1313

1414
Throughout the lifecycle of your Azure Kubernetes Service (AKS) cluster, you may need to access an AKS Windows Server node. This access could be for maintenance, log collection, or other troubleshooting operations. You can access the AKS Windows Server nodes using RDP. For security purposes, the AKS nodes aren't exposed to the internet.
1515

16-
Alternatively, if you want to SSH to your AKS Windows Server nodes, you'll need access to the same key-pair that was used during cluster creation. Follow the steps in [SSH into Azure Kubernetes Service (AKS) cluster nodes][ssh-steps].
16+
Alternatively, if you want to SSH to your AKS Windows Server nodes, you need access to the same key-pair that was used during cluster creation. Follow the steps in [SSH into Azure Kubernetes Service (AKS) cluster nodes][ssh-steps].
1717

1818
This article shows you how to create an RDP connection with an AKS node using their private IP addresses.
1919

@@ -61,7 +61,7 @@ The following example creates a virtual machine named *myVM* in the *myResourceG
6161

6262
### [Azure CLI](#tab/azure-cli)
6363

64-
You'll need to get the subnet ID used by your Windows Server node pool. The commands below will query for the following information:
64+
You need to get the subnet ID used by your Windows Server node pool and query for:
6565
* The cluster's node resource group
6666
* The virtual network
6767
* The subnet's name
@@ -103,7 +103,7 @@ Record the public IP address of the virtual machine. You'll use this address in
103103

104104
### [Azure PowerShell](#tab/azure-powershell)
105105

106-
You'll need to get the subnet ID used by your Windows Server node pool. The commands below will query for the following information:
106+
You'll need to get the subnet ID used by your Windows Server node pool and query for:
107107
* The cluster's node resource group
108108
* The virtual network
109109
* The subnet's name and address prefix
@@ -154,7 +154,7 @@ The following example output shows the VM has been successfully created and disp
154154
13.62.204.18
155155
```
156156

157-
Record the public IP address of the virtual machine. You'll use this address in a later step.
157+
Record the public IP address of the virtual machine and use the address in a later step.
158158

159159
---
160160

@@ -271,7 +271,7 @@ Connect to the public IP address of the virtual machine you created earlier usin
271271

272272
![Image of connecting to the virtual machine using an RDP client](media/rdp/vm-rdp.png)
273273

274-
After you've connected to your virtual machine, connect to the *internal IP address* of the Windows Server node you want to troubleshoot using an RDP client from within your virtual machine.
274+
After you have connected to your virtual machine, connect to the *internal IP address* of the Windows Server node you want to troubleshoot using an RDP client from within your virtual machine.
275275

276276
![Image of connecting to the Windows Server node using an RDP client](media/rdp/node-rdp.png)
277277

0 commit comments

Comments
 (0)