-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: seamless integration inside vnet #1391
Comments
Thank you for contacting us @havarnov. This feature sounds like a contradictory request. It would be helpful to understand a little more about what your ultimate end goal is. If you simply have an environment which you just want to expose internally then switching the environment to "internal" and allowing connections from everywhere (on your app's ingress) should get your what you need, I things. It's confusing, but making your environment internal will overwrite any ingress settings to be limited to those confines. Hope this helps, otherwise please add some additional context so we can help you better. |
Sorry, I'll try to explain better. Our Container App Environment is public, and must be since we have lots of services that are exposed to the internet. But some services are internal only, as in only our services should be able to access them. This works fine if all services are inside the same Container App Environment, but other services can't access those internal services. This is our case with Azure Function Apps, which we now host on the new flex hosting plan. Those Functions Apps can be placed inside the same virtual network as the Container App Environment, but AFAIK there's no easy way for those Functions Apps to access the internal services (hosted in out Container App Environment). I guess one option would be to set our Container App Environment to internal access only and explicitly expose our public services with a Private Link to Azure Front Door? |
It would be nice if it was possible to access Azure Container Apps from within the vnet, even if "Limited to Container Apps Environment" is selected.
Typical use case:
The text was updated successfully, but these errors were encountered: