Share via

On AKS Backend Pool is empty

Sreekumar SK 0 Reputation points
2025-02-17T02:30:16.8066667+00:00

I have deployed application gateway as my Ingress, backend pool doesn't have any targets, its coming empty. My pods are getting IP's and accessible the application within the cluster. Backend pool is not getting updated.

User's image

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,278 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vidya Viraktamath 550 Reputation points Microsoft Employee
    2025-02-17T08:11:45.5666667+00:00
    1. Ingress: Verify Ingress annotations (kubernetes.io/ingress.class: azure/application-gateway), service name/port, and path rules.
    2. AGIC: Check AGIC logs (kubectl logs -n kube-system <agic-pod>) for errors. Restart AGIC if needed.
    3. Service: Ensure service selector matches pod labels (kubectl get pods --show-labels, kubectl describe service <service>).
    4. Pods: Confirm pod IPs are in the Application Gateway's VNET (kubectl get pods -o wide).
    5. Azure Portal: Check Application Gateway backend pool health, listener, and rules, verify health probe path/port in service/ingress matches app, Check NSGs/UDRs for conflicts.
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.