Forum Discussion
how to connect to container app via s2s vpn
I am not sure what you mean by:
Created a ContainerApp Environment with defined non-internal virtual network with a subnet.
I am presuming the ContainerApp Environment is injected into the vnet that your vpn gateway is in, with an internal loadbalancer? (or in a vnet peered to that?)
You also say: I can't see a way of connecting the subnet used for the container to be a subnet accessible from the VPN.
This also seems to indicate that you did not inject the environment into a custom vnet.
Can you elaborate a little more?
- AndreG
thanks for the response
I don't really undertsand what you mean by "injected into the vnet that your vpn gateway is in, with an internal loadbalancer". This probably shows a lack in my understanding to what I need.
Can you expian it a bit more or provide a detailed reference ?
Thanks
PeterIn your original message you state 4 points that you have done. In point 1 you state you have created a S2S VPN connection which connects your office with that Azure Cloud. That means you have a VNet, with (at least) a VPN Gateway.
How is this VNet connected to the Container App Environment?
How I would do this, is to deploy the ACA environment in a https://learn.microsoft.com/en-us/azure/container-apps/vnet-custom?tabs=bash%2Cazure-cli&pivots=azure-portal, possibly with an https://learn.microsoft.com/en-us/azure/container-apps/networking?tabs=workload-profiles-env%2Cazure-cli#custom-vnet-configuration. This could be a subnet within the same VNet that your VPN GW is deployed in or another VNet peered to that one.
This should allow you to make the containers available over the S2S connection, providing you also take care of the proper DNS name resolution.
