Skip to content

Commit f35e2bd

Browse files
committed
link snafu
1 parent 5e58a8c commit f35e2bd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/private-clusters.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -135,8 +135,8 @@ Where *--enable-private-cluster* is a mandatory flag for a private cluster.
135135
The API server endpoint has no public IP address. To manage the API server, you will need to use a VM that has access to the AKS cluster's Azure Virtual Network (VNet). There are several options for establishing network connectivity to the private cluster.
136136

137137
* Create a VM in the same Azure Virtual Network (VNet) as the AKS cluster.
138-
* Use a VM in a separate network and set up [Virtual network peering](virtual-network-peering). See the section below for more information on this option.
139-
* Use an [Express Route or a VPN](express-route-or-VPN) connection.
138+
* Use a VM in a separate network and set up [Virtual network peering][virtual-network-peering]. See the section below for more information on this option.
139+
* Use an [Express Route or VPN][express-route-or-VPN] connection.
140140

141141
Creating a VM in the same VNET as the AKS cluster is the easiest option. Express Route and VPNs add costs and require additional networking complexity. Virtual network peering requires you to plan your network CIDR ranges to ensure there are no overlapping ranges.
142142

0 commit comments

Comments
 (0)