Skip to content

Commit 90472b3

Browse files
Overlay clarification
1 parent b5de55a commit 90472b3

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/application-gateway/tutorial-ingress-controller-add-on-existing.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,9 @@ To configure more parameters for the above command, see [az aks create](/cli/azu
5757
>[!NOTE]
5858
>If you are planning on using AGIC with an AKS cluster using CNI Overlay, specify the parameter `--aks-custom-headers AKSHTTPCustomFeatures=Microsoft.ContainerService/AppGatewayWithOverlayPreview` to configure AGIC to handle connectivity to the CNI Overlay enabled cluster.
5959
60+
>[!WARNING]
61+
>This document assumes Azure CNI is installed in the AKS cluster. If you are planning on using CNI Overlay, you must ensure Application Gateway and the AKS cluster are part of the same virtual network.
62+
6063
## Deploy a new application gateway
6164

6265
You'll now deploy a new application gateway, to simulate having an existing application gateway that you want to use to load balance traffic to your AKS cluster, **myCluster**. The name of the application gateway will be **myApplicationGateway**, but you'll need to first create a public IP resource, named **myPublicIp**, and a new virtual network called **myVnet** with address space 10.0.0.0/16, and a subnet with address space 10.0.0.0/24 called **mySubnet**, and deploy your application gateway in **mySubnet** using **myPublicIp**.

0 commit comments

Comments
 (0)