Skip to content

Commit 1bc5f52

Browse files
committed
update per PR review
1 parent 1ebe4bd commit 1bc5f52

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/api-server-vnet-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ An Azure Kubernetes Service (AKS) cluster with API Server VNet Integration confi
1515

1616
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
1717

18-
## API Server Connectivity
18+
## API server connectivity
1919

2020
The control plane or API server is in an Azure Kubernetes Service (AKS)-managed Azure subscription. A customer's cluster or node pool is in the customer's subscription. The server and the virtual machines that make up the cluster nodes can communicate with each other through the API server VIP and pod IPs that are projected into the delegated subnet.
2121

2222
At this time, API Server VNet integration is only supported for private clusters. Unlike standard public clusters, the agent nodes communicate directly with the private IP address of the ILB VIP for communication to the API server without using DNS. External clients needing to communicate with the cluster should follow the same private DNS setup methodology as standard [private clusters](private-clusters.md).
2323

2424
## Region availability
2525

26-
API Server VNet Integration is available in the following regions at this time. More will be added as available:
26+
API Server VNet Integration is available in the following regions at this time:
2727

2828
- canary regions
2929
- eastus2

0 commit comments

Comments
 (0)