I am having trouble figuring out how to achieve this.
I have deployed Consul in a K8s cluster.
I can successfully join a Consul agent running on a VM outside K8s (configured to expose gossip etc.).
When I want to access a service inside K8s, envoy of course tries to route that request to the pod IP, but the pod IP is not routable from outside K8s.
I have read the documentation but cannot understand if any type of gateway can solve this problem or if I have to deploy multiple datacenters and have gateways between them in this scenario, I would really like to not have to deploy multiple datacenters.
Hi @johanlundberg92,
Considering they are part of the same Consul cluster, the services are expected to be reachable between each other on a flat network. So, in your case, splitting into multiple DCs would be the only solution.
However, the enterprise version of Consul provides a few other options, such as Admin Partitions, Network Segments, etc., that make this possible.