Creating an Azure Application Gateway Ingress Controller for AKS

3 min readAug 25, 2024

⚠️This article is just one part of a comprehensive article on Setting Up Kubernetes (AKS) with Azure Application Gateway Ingress Controller.

Here’s a step-by-step guide on how to create an Azure Application Gateway Ingress Controller (AGIC) using the Azure Portal:

Create the Application Gateway

Navigate to Application Gateways in the Azure Portal, and click + Create.

You can leave default values if you don't need to change it

Choose or Create a Virtual Network

Using an Existing Virtual Network:
If you already have a VNet configured for your AKS, you should select this existing VNet. This setup allows seamless integration between your Application Gateway and AKS.
Creating a New Virtual Network:
If you don’t have a suitable VNet, you can create a new one during the Application Gateway setup. Click on the Create new option next to the Virtual Network dropdown.
Provide a name for the new VNet, specify the address space, and create the necessary subnets.

Subnet Creation for Application Gateway:

Once you’ve selected or created the VNet, you need to create a dedicated subnet specifically for the Application Gateway. This subnet is where the Application Gateway will reside.
Ensure the subnet has enough IP addresses to handle the scaling of the Application Gateway, especially if you plan to scale the gateway instances in the future.

By following these steps, you ensure that your Application Gateway is properly integrated within your network infrastructure, allowing for efficient traffic management and security in conjunction with your AKS cluster.

Next, Create a Public IP Address. This public IP will be associated with your Application Gateway, making it accessible over the internet.

Next, Add a default backend pool with the default values; the Ingress file will overwrite it later with its specified values. Create a default routing rule with the default values as shown below: