I have encountered a bug in the current deployment of two Azure Container Apps with simple-hello-world-container
image, where one is situated in the eastus region, and the other is in eastus2. Both container applications have been properly configured with Virtual Network (VNET) integration and are designed to be externally accessible.
As part of the deployment optimization, a cross-region load balancer was introduced. Within its backend pool, I included the frontend IP configurations of regional standard load balancers from both aca-eastus and aca-eastus2. To ensure seamless communication, I aligned the backend port of the load balancing rule on the cross-region load balancer with the frontend port of the load balancing rule on the regional standard load balancers.
Despite the cross-region load balancer indicating a healthy status, there is an observed issue where the services hosted on these containers are not accessible via the public IP address associated with the cross-region load balancer.
I have verified and confirmed that no Network Security Group (NSG) is blocking access from the cross-region load balancer to the internal load balancer.
Expected behavior [What you expected to happen.]
Services Should be accessible on Public IP of cross region load balancer
Actual behavior [What actually happened.]
Screenshots
Additional context
Ex. Did this issue occur in the CLI or the Portal?
Issue description
I have encountered a bug in the current deployment of two Azure Container Apps with simple-hello-world-container image, where one is situated in the eastus region, and the other is in eastus2. Both container applications have been properly configured with Virtual Network (VNET) integration and are designed to be externally accessible.
As part of the deployment optimization, a cross-region load balancer was introduced. Within its backend pool, I included the frontend IP configurations of regional standard load balancers from both aca-eastus and aca-eastus2. To ensure seamless communication, I aligned the backend port of the load balancing rule on the cross-region load balancer with the frontend port of the load balancing rule on the regional standard load balancers.
Despite the cross-region load balancer indicating a healthy status, there is an observed issue where the services hosted on these containers are not accessible via the public IP address associated with the cross-region load balancer.
I have verified and confirmed that no Network Security Group (NSG) is blocking access from the cross-region load balancer to the internal load balancer.
Expected behavior [What you expected to happen.] Services Should be accessible on Public IP of cross region load balancer
Actual behavior [What actually happened.]
Screenshots
Additional context
Ex. Did this issue occur in the CLI or the Portal?