0

I'm struggling trying to solve a problem of setting up an NGINX as a container with external access and routing traffic to different vnets.

I'm aware that a container instance cannot have an external IP. But when using a container app instead, the container gets an ip in the 100.x.x.x, due to it being externally exposed, meaning it doesn't use the subnet that have been defined for it.

So what I see as solutions are:

  1. Application gateway for the nginx container (doesn't seem to make sense as the Application gateway does the same as nginx as I understand)

  2. Create a load balancer routing the traffic to the NGINX container instance which has access to the other VNET's as it has an internal IP.

Are there other possiblities besides using the NGINXaas available in the Azure marketplace (for me the pricing is rather difficult to figure out).

Is option 2 even possible ?

Thank you :)

Improve this question

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.