Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 993fca8

Browse files
authoredMay 27, 2022
Update private-clusters.md
1 parent 8ad4711 commit 993fca8

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed
 

‎articles/aks/private-clusters.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create a private Azure Kubernetes Service cluster
33
description: Learn how to create a private Azure Kubernetes Service (AKS) cluster
44
services: container-service
55
ms.topic: article
6-
ms.date: 01/12/2022
6+
ms.date: 05/27/2022
77

88
---
99

@@ -150,6 +150,9 @@ As mentioned, virtual network peering is one way to access your private cluster.
150150

151151
3. In scenarios where the VNet containing your cluster has custom DNS settings (4), cluster deployment fails unless the private DNS zone is linked to the VNet that contains the custom DNS resolvers (5). This link can be created manually after the private zone is created during cluster provisioning or via automation upon detection of creation of the zone using event-based deployment mechanisms (for example, Azure Event Grid and Azure Functions).
152152

153+
> [!NOTE]
154+
> Conditional Forwarding doesn't support subdomains.
155+
153156
> [!NOTE]
154157
> If you are 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 Cluster, the cluster creation will fail. You will 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, in order to make the creation successful.
155158

0 commit comments

Comments
 (0)
Please sign in to comment.