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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,8 +135,8 @@ Where *--enable-private-cluster* is a mandatory flag for a private cluster.
135
135
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.
136
136
137
137
* 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.
140
140
141
141
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.
0 commit comments