Connect load balancer to container instance inside a vertual network

Kessler, Avi 1 Reputation point
2020-11-01T07:42:22.7+00:00

Hi,
I'm relatively new to Azure.
we are trying to POC a simple scenario of several container instances in the same virtual network and subnet.
we want one of the containers to be exposed from a public internet (inbound web service).

In order to do this, I set up a load balancer with a public ip.
But when I build the backend pool and connect it to the virtual network we can't find any virtual machine.

am I missing a step?

Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
643 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,158 questions
Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
404 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. suvasara-MSFT 10,006 Reputation points
    2020-11-01T08:28:06.027+00:00

    @Kessler, Avi , Placing an Azure Load Balancer in front of container instances in a networked container group is not supported. The feature of adding backend pool by IP address and virtual network is not currently supported for ACI containers.

    ----------

    Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.

  2. Abdallah Bakir 0 Reputation points
    2024-03-21T09:53:02.56+00:00

    Hello, Actually I found myself in the same trouble and I do not know how to solve it . I need to deploy container instance cluster behind load balancer in a private vnet for TCP communications. I tried to use the static ip of azure container instance as backend pool for the load balancer but the LB does not transfer request to the container instance . Also, tried Azure container apps , but I found another problem dealing with the change of the request source IP .

    0 comments