Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
Application Gateway Ingress Controller, BackEnd pools are not been created automatically when you deploy new pods in AKS.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 6%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EES%3C/text%3E%3C/svg%3E)
Ely Saul Vicente Espinal
0
Reputation points
I am creating a new architecture using Bicep Templates, I am creating an Application Gateway to be used as Ingress Controller by an AKS cluster, I have added all the permissions posted in the tutorials, but everytime I deploy new pods and the ingress controller, the Application Gateway's backend pool is no updated automatically, I have tried lot of different options and nothing works. Can you help with this problem.
Azure Kubernetes Service
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 64%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Durga Reshma Malthi 9,595 Reputation points Microsoft External Staff Moderator2025-08-08T13:34:43.55+00:00 When using Azure Application Gateway as an Ingress Controller for an Azure Kubernetes Service (AKS) cluster, it is essential to ensure that the Application Gateway is correctly configured to automatically update its backend pool with the IP addresses of the pods.
- Ensure that your Ingress resources and the Application Gateway Ingress Controller (AGIC) are correctly annotated.
- Ensure that the Application Gateway Ingress Controller is deployed correctly in your AKS cluster.
kubectl get pods -n kube-system -l app=ingress-azure - Ensure you have Contributor role on the Application Gateway. It has Reader role on the AKS cluster's resource group.
- Ensure that your Ingress resource is correctly defined and that it points to the correct services and paths
Bicep Template Sample: Refer to this document - https://learn.microsoft.com/en-us/azure/templates/microsoft.network/applicationgateways?pivots=deployment-language-bicep
Hope this helps!
Please Let me know if you have any queries.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 94%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Akram Kathimi 1,751 Reputation points Microsoft Employee2025-08-10T12:08:08.94+00:00 you need to check the appgw controller pod logs in kube-system. The log should clearly show you what the problem is.
Sign in to comment
Sign in to answer