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/private-clusters.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Private cluster is available in public regions, Azure Government, and Azure Chin
41
41
42
42
### Create a resource group
43
43
44
-
Create a resource group using the[`az group create`][az-group-create] command. You can also use an existing resource group for your AKS cluster.
44
+
Create a resource group using the[`az group create`][az-group-create] command. You can also use an existing resource group for your AKS cluster.
45
45
46
46
```azurecli-interactive
47
47
az group create -l eastus -n myResourceGroup
@@ -177,7 +177,7 @@ Virtual network peering is one way to access your private cluster. To use virtua
177
177
> Conditional Forwarding doesn't support subdomains.
178
178
179
179
> [!NOTE]
180
-
> If you're using [bring your own route table with kubenet](./configure-kubenet.md#bring-your-own-subnet-and-route-table-with-kubenet) and bring your own DNS with private clusters, the cluster creation will fail. You need to associate the [``RouteTable](./configure-kubenet.md#bring-your-own-subnet-and-route-table-with-kubenet) in the node resource group to the subnet after the cluster creation failed to make the creation successful.
180
+
> If you're using [bring your own route table with kubenet](./configure-kubenet.md#bring-your-own-subnet-and-route-table-with-kubenet) and bring your own DNS with private clusters, the cluster creation will fail. You need to associate the [`RouteTable`](./configure-kubenet.md#bring-your-own-subnet-and-route-table-with-kubenet) in the node resource group to the subnet after the cluster creation failed to make the creation successful.
181
181
182
182
## Use a private endpoint connection
183
183
@@ -205,18 +205,18 @@ Create a private endpoint resource in your VNet:
205
205
> [!IMPORTANT]
206
206
> Check that the region selected is the same as the virtual network where you want to connect from, otherwise you won't see your virtual network in the **Configuration** tab.
207
207
208
-
1. Select **Next: Resource** and set up the following options:
208
+
6. Select **Next: Resource** and set up the following options:
209
209
***Connection method**: Select *Connect to an Azure resource in my directory.*
210
210
***Subscription**: Select the subscription where your private cluster is located.
0 commit comments