Skip to content
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

Open
havarnov opened this issue Jan 22, 2025 · 2 comments
Open

Feature Request: seamless integration inside vnet #1391

havarnov opened this issue Jan 22, 2025 · 2 comments

Comments

@havarnov
Copy link

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:

  • internal HTTP service deployed as a Azure Container App with internal ingress only.
  • Azure Funtions App (flex) with vnet integration should be able to call the internal HTTP service.
@havarnov havarnov added the enhancement New feature or request label Jan 22, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 Pending a first pass to read, tag, and assign label Jan 22, 2025
@simonjj
Copy link
Collaborator

simonjj commented Jan 23, 2025

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.
If you want to still serve a few external apps we recommend you setup your vNet routing to allow ingress to the appropriate app.

Hope this helps, otherwise please add some additional context so we can help you better.

@simonjj simonjj added Needs: Author Feedback and removed enhancement New feature or request Needs: triage 🔍 Pending a first pass to read, tag, and assign labels Jan 23, 2025
@havarnov
Copy link
Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants