An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
Hello @cargobuddy,
Thank you for reaching out to Microsoft Q&A.
As discussed, offline, we observed that the Application Gateway was configured with only a public IP address, while the AKS cluster was deployed with private access only and does not have a public endpoint enabled.
In this scenario, if the AKS cluster is intended to be accessed using a private IP, the Application Gateway must also have a private frontend IP configuration in addition to the public IP.
After adding a private IP configuration to the Application Gateway and restarting the Ingress Controller, the issue was resolved.
The AKS backend pool is now being automatically detected and populated in the Application Gateway as expected.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".