Examine ingress settings for traffic-splitting and blue-green deployments
Azure Container Apps allows you to expose your container app to the public web, your virtual network (VNET), and other container apps within your environment by enabling ingress. Ingress settings are enforced through a set of rules that control the routing of external and internal traffic to your container app. When you enable ingress, you don’t need to create an Azure Load Balancer, public IP address, or any other Azure resources to enable incoming HTTP requests or TCP traffic.
Ingress supports:
- External and internal ingress.
- HTTP and TCP ingress types.
- Domain names.
- IP restrictions.
- Authentication.
- Traffic splitting between revisions.
- Session affinity.
Enable ingress
You can configure ingress for your container app using the Azure CLI, an Azure Resource Manager template, or the Azure portal.
You can enable ingress when you create your container app, or you can enable ingress for an existing container app.
- To configure ingress when you create your container app, select Ingress from the App Configuration tab of the container app creation wizard.
- To configure ingress for an existing container app, select Ingress from left-side menu of the container app resource page.
When you enable ingress, you can choose between two types of ingress:
- External: Accepts traffic from both the public internet and your container app’s internal environment.
- Internal: Allows only internal access from within your container app’s environment.
Each container app within an environment can be configured with different ingress settings.