Skip to content

Commit df939de

Browse files
committed
Resolving blocking issues
1 parent 9813270 commit df939de

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/aks/private-clusters.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Private cluster is available in public regions, Azure Government, and Azure Chin
4141

4242
### Create a resource group
4343

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

4646
```azurecli-interactive
4747
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
177177
> Conditional Forwarding doesn't support subdomains.
178178
179179
> [!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.
181181
182182
## Use a private endpoint connection
183183

@@ -205,18 +205,18 @@ Create a private endpoint resource in your VNet:
205205
> [!IMPORTANT]
206206
> 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.
207207
208-
1. Select **Next: Resource** and set up the following options:
208+
6. Select **Next: Resource** and set up the following options:
209209
* **Connection method**: Select *Connect to an Azure resource in my directory.*
210210
* **Subscription**: Select the subscription where your private cluster is located.
211211
* **Resource type**: Select *Microsoft.ContainerService/managedClusters*.
212212
* **Resource**: Select your private cluster.
213213
* **Target sub-resource**: Select *management*.
214-
2. Select **Next: Virtual Network** and set up the following options:
214+
7. Select **Next: Virtual Network** and set up the following options:
215215
* **Networking**:
216216
* **Virtual network**: Select your virtual network.
217217
* **Subnet**: Select your subnet.
218-
3. Select **Next: DNS** > **Next: Tags** and (optionally) set up key-values as needed.
219-
4. Select **Next: Review + create** > **Create**.
218+
8. Select **Next: DNS** > **Next: Tags** and (optionally) set up key-values as needed.
219+
9. Select **Next: Review + create** > **Create**.
220220

221221
Once the resource is created, record the private IP address of the private endpoint for future use.
222222

0 commit comments

Comments
 (0)