Integrating Azure Front Door with Application Gateway for Containers

v-jrehman 

 

Try refer this:

 

https://techcommunity.microsoft.com/t5/apps-on-azure-blog/integrating-workload-profile-container-app-with-front-door-and/ba-p/4217335

 

Application Gateway for Containers Setup
Ensure your Azure Application Gateway for Containers is set up and is managing the traffic for your containerized applications through its internal load balancing functionality.
Make sure that the Application Gateway has been correctly configured for HTTP routing for your containers.
2. Create an Azure Front Door Profile
In the Azure Portal, create an Azure Front Door profile.
Define a Frontend endpoint that will represent your global entry point. This will handle incoming requests.
3. Configure Backend Pool with Application Gateway
In Azure Front Door, define a Backend pool where you add the Application Gateway as the backend service.
Use the public IP address of the Application Gateway for Containers as the backend.
Ensure that the backend pool's settings, such as health probes and routing methods, are compatible with your Application Gateway setup.
4. Backend Health Probes
Set up health probes in Azure Front Door that will check the availability of the Application Gateway.
Ensure that the health probe routes are correctly configured to a valid endpoint in your Application Gateway.
5. Routing Rules
In Azure Front Door, configure Routing Rules to forward incoming traffic to the Application Gateway for Containers.
You can define rules based on URL patterns to distribute traffic between different services managed by the Application Gateway.
6. TLS Termination
If using TLS, decide where to handle TLS termination. You can either:
Terminate TLS at Azure Front Door and forward HTTP traffic to Application Gateway.
Allow TLS pass-through and terminate at Application Gateway.
7. Firewall Rules
Ensure that both Azure Front Door and Application Gateway have the necessary firewall and network security group (NSG) rules to allow traffic between them.
Troubleshooting Steps
Double-check that the public IP of the Application Gateway is correctly configured in the Front Door backend pool.
Verify that the health probes from Front Door are correctly configured to check the status of the Application Gateway’s endpoints.
If using the "Managed by ALB Controller" process, make sure that the Application Gateway Ingress Controller (AGIC) is correctly set up and managing your Kubernetes cluster.