An Azure service that provides a general-purpose, serverless container platform.
Hello @CY Lee
As of now, Azure Container Apps provides two options for ingress:
- Accepting traffic from anywhere (external ingress)
- Limiting traffic to the Container Apps Environment (internal ingress).
The "Limited to VNet" option that you’ve referenced might have been part of older configurations or discussions. In recent changes, Azure has streamlined ingress options for ease of use, and it appears the direct granularity of limiting access specifically to a VNet is not explicitly provided in the newer implementation.
For environments that require this level of control, you can effectively achieve a similar outcome by configuring your ingress settings and leveraging Azure's VNet integration:
- Deploy your Container Apps environment to a VNet: This will ensure that your application can only be accessed from within the designated network.
- Utilize network security groups (NSGs) to enforce policies that restrict traffic based on your needs.
In case you are looking to further enhance your ingress control:
- Consider using additional Azure services like Azure Application Gateway or Azure Front Door for advanced routing setups.
- You can configure IP restrictions to further refine who can access your application.
Please find the documentation below:
https://learn.microsoft.com/en-us/azure/container-apps/ingress-overview
https://learn.microsoft.com/en-us/azure/container-apps/ingress-how-to?pivots=azure-cli