How can I set up an Azure Application Gateway to use Azure Container Instances as a dynamic backend target? Currently, I’ve assigned a private IP address of the container as the target, but I face an issue since this IP changes with each deployment. I’m looking for a more flexible solution, such as utilizing a tag for the container. Here are the options I am considering. Is it feasible to achieve this with Azure Application Gateway, or should I consider alternative methods? I’ve attempted to configure the backend using IPs, but they are not stable across deployments.
Interesting problem, Zoe! Wondering if you’ve looked into configuring a private endpoint with containers and App Gateway? That way, changes in the container IP might not impact your setup as much. Would love to hear others’ thoughts on this or any experiences you’ve had using different approaches!
hey Zoe, u might wanna try using Azure’s Application Gateway with Azure Kubernetes Service for more seamless integration. Kubernetes has built-in service discovery to handle dynamic IPs. If that’s beyond ur scope, using Azure DNS with ACI could provide some resilincy against IP changes. hope this helps!
An approach worth considering is leveraging Azure Service Fabric to manage the lifecycle and networking of your application. Service Fabric provides built-in DNS service, which might suit your requirement for dynamic addressing without worrying about changing IPs. It allows you to deploy containers, manage networking between them, and expose a stable DNS entry for each service, which could help mitigate your current problem. This solution also adds the advantage of having a more robust orchestration platform.