Skip to content

Commit 2e016f6

Browse files
authored
Merge pull request #98808 from mlearned/mlearned-aks-private-clusters-911-charlies
fixes per saurya
2 parents 7ad5988 + fcf77e6 commit 2e016f6

File tree

1 file changed

+26
-21
lines changed

1 file changed

+26
-21
lines changed

articles/aks/private-clusters.md

Lines changed: 26 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,12 @@
22
title: Private Azure Kubernetes Service cluster
33
description: Learn how to create a private Azure Kubernetes Service (AKS) cluster
44
services: container-service
5-
author: saudas
6-
manager: saudas
5+
author: mlearned
76

87
ms.service: container-service
98
ms.topic: article
109
ms.date: 12/10/2019
11-
ms.author: saudas
10+
ms.author: mlearned
1211
---
1312

1413
# Public Preview - Private Azure Kubernetes Service cluster
@@ -38,13 +37,15 @@ The communication between the control plane/API server, which is in an AKS-manag
3837

3938
## Install latest AKS CLI preview extension
4039

41-
You need the **aks-preview 0.4.18** extension or later.
40+
To use private clusters, you need the *aks-preview* CLI extension version 0.4.18 or higher. Install the *aks-preview* Azure CLI extension using the [az extension add][az-extension-add] command, then check for any available updates using the [az extension update][az-extension-update] command::
4241

4342
```azurecli-interactive
44-
az extension update --name aks-preview
45-
az extension list
46-
```
43+
# Install the aks-preview extension
44+
az extension add --name aks-preview
4745
46+
# Update the extension to make sure you have the latest version installed
47+
az extension update --name aks-preview
48+
```
4849
> [!CAUTION]
4950
> When you register a feature on a subscription, you can't currently un-register that feature. After you enable some preview features, defaults may be used for all AKS clusters then created in the subscription. Don't enable preview features on production subscriptions. Use a separate subscription to test preview features and gather feedback.
5051
@@ -74,17 +75,18 @@ az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --lo
7475
Where --enable-private-cluster is a mandatory flag for a private cluster
7576

7677
#### Advanced Networking
77-
```azurecli-interactive
78-
az aks create \
79-
--resource-group <private-cluster-resource-group> \
80-
--name <private-cluster-name> \
81-
--load-balancer-sku standard \
82-
--enable-private-cluster \
83-
--network-plugin azure \
84-
--vnet-subnet-id <subnet-id> \
85-
--docker-bridge-address 172.17.0.1/16 \
86-
--dns-service-ip 10.2.0.10 \
87-
--service-cidr 10.2.0.0/24
78+
79+
```azurecli-interactive
80+
az aks create \
81+
--resource-group <private-cluster-resource-group>\
82+
--name <private-cluster-name> \
83+
--load-balancer-sku standard
84+
--enable-private-cluster
85+
--network-plugin azure \
86+
--vnet-subnet-id <subnet-id> \
87+
--docker-bridge-address 172.17.0.1/16 \
88+
--dns-service-ip 10.2.0.10 \
89+
--service-cidr 10.2.0.0/24 \
8890
```
8991
Where --enable-private-cluster is a mandatory flag for a private cluster
9092

@@ -93,9 +95,9 @@ The API server end point has no public IP address. Consequently, users will need
9395

9496
* Get credentials to connect to the cluster
9597

96-
```azurecli-interactive
97-
az aks get-credentials --name MyManagedCluster --resource-group MyResourceGroup
98-
```
98+
```azurecli-interactive
99+
az aks get-credentials --name MyManagedCluster --resource-group MyResourceGroup
100+
```
99101
* Create a VM in the same VNET as the AKS cluster or create a VM in a different VNET and peer this VNET with the AKS cluster VNET
100102
* If you create a VM in a different VNET, you'll need to set up a link between this VNET and the Private DNS Zone
101103
* go to the MC_* resource group in the portal
@@ -116,7 +118,10 @@ az aks get-credentials --name MyManagedCluster --resource-group MyResourceGroup
116118
* No support to convert existing AKS clusters to private clusters
117119
* Deleting or modifying the private endpoint in the customer subnet will cause the cluster to stop functioning
118120
* Azure Monitor for containers Live Data isn't currently supported
121+
* Bring your own DNS isn't currently supported
119122

120123
<!-- LINKS - internal -->
121124
[az-provider-register]: /cli/azure/provider?view=azure-cli-latest#az-provider-register
122125
[az-feature-list]: /cli/azure/feature?view=azure-cli-latest#az-feature-list
126+
[az-extension-add]: /cli/azure/extension#az-extension-add
127+
[az-extension-update]: /cli/azure/extension#az-extension-update

0 commit comments

Comments
 (0)