Mastering Ingress in Azure Container Apps: What You Need to Know

Ingress settings in Azure Container Apps are essential for controlling how traffic flows to your applications. They allow you to define rules for both external and internal traffic, ensuring that your container apps can communicate securely and efficiently. This is particularly important in a microservices architecture where services need to interact seamlessly.

When you enable ingress, you can choose between external and internal types. External ingress accepts traffic from the public internet as well as from within your app's environment, while internal ingress restricts access to only internal sources. Azure Container Apps supports both HTTP and TCP ingress types, allowing for a wide range of protocols. You can also configure session affinity, which routes all HTTP requests from a client to the same container app replica, enhancing user experience. Traffic splitting between active revisions is another powerful feature, enabling you to test new versions without downtime.

In production, be aware that external TCP ingress is only supported in environments using a virtual network. Also, port number 36985 is reserved for internal health checks, so avoid using it for your applications. To expose additional TCP ports, ensure you have the container apps CLI extension installed. Keeping these details in mind will help you avoid common pitfalls and optimize your ingress configurations.