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

Ingress in Azure Container Apps is essential for directing traffic to your applications, whether from the public internet or internally within your environment. This capability allows you to expose your apps securely and efficiently, addressing the need for controlled access in cloud-native architectures.

When you enable ingress, you can choose between external and internal types. External ingress exposes your app through the environment's inbound IP address, making it accessible from the public internet. In contrast, internal ingress restricts access to within the same Container Apps environment. Azure supports both HTTP and TCP protocols for ingress. HTTP ingress offers features like TLS termination, support for HTTP/1.1 and HTTP/2, and automatic redirection from HTTP to HTTPS, while TCP ingress allows for broader protocol support, enabling access to other container apps in the same environment.

In production, be mindful of the limitations. External TCP ingress is only available for environments using a virtual network, and port 36985 is reserved for internal health checks, which can lead to confusion if you're not careful. Ensure you have the container apps CLI extension for exposing additional TCP ports. These nuances can significantly impact your deployment strategy and application performance.