search

nicholasjackson / docker-consul-envoy

Docker image with Consul and Envoy
MIT License
30 stars 24 forks source link

Connecting to consul causes total failure. #10

Closed codex70 closed 1 year ago

codex70 commented 1 year ago

I'm not sure whether I'm even using this correctly, or whether it's the correct tool for the job. I need to connect a system that is on a standalone VM with consul running in a kubernetes cluster.

I have consul setup inside a kubernetes cluster using service mesh and everything works as expected from inside the kubernetes cluster. I then have separate services hosted on standalone VMs outside of the kubernetes cluster that I would like to connect to the service mesh.

I am using docker to run an agent locally on the VM, which connects to the consul datacenter inside the cluster. This appears to work as expected and I can then register services with Consul, but obviously am unable to connect using the service mesh.

When I use the image from this repository to connect to the local agent, it appears to connect OK, and even registers the service as inside the service mesh, but then the whole systems enters into a catastrophic failure.

Other services cannot connect to the new service across the service mesh, but even more importantly, existing service mesh services are no longer able to communicate. Ingress controllers stop working with the ingress reporting 502 errors and I am unable to start any new services (or redeploy existing services) inside the service mesh in kubernetes.

It feels like I'm missing something obvious, am I just using this for completely the wrong thing, or is it a simple miss-configuration? If you have any ideas, let me know.

codex70 commented 1 year ago

I did find a solution, but it's quite complicated and requires the implementation of service mesh across datacenters. I will close the issue.