You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've now got a Mesh application up and running with a couple of services. However, they're currently sat there on the open internet, since all the guides and docs seem to use this scenario in their examples.
I think where I want to get to is:
The service mesh services on their own internal-to-Azure network
An Azure API Management instance facing the public internet, authenticating, logging and routing requests into the mesh network
Plus, the Mesh network being able to communicate with our on-prem SQL servers (I believe we have a VNET which already links on-prem with Azure)
Are there any guides (or can anyone offer some examples) on how to construct the JSON/YAML deployment templates to achieve this?
Thanks!
Chris
The text was updated successfully, but these errors were encountered:
Any comment on this? I've since been told by support that Azure API Management doesn't work with Mesh, but I've been told by Azure support that on-prem connectivity and limiting access to the application to connections originating on-prem was supported.
Hi,
I've now got a Mesh application up and running with a couple of services. However, they're currently sat there on the open internet, since all the guides and docs seem to use this scenario in their examples.
I think where I want to get to is:
Are there any guides (or can anyone offer some examples) on how to construct the JSON/YAML deployment templates to achieve this?
Thanks!
Chris
The text was updated successfully, but these errors were encountered: