This repository has been archived by the owner on Aug 25, 2021. It is now read-only.
Unable to access consul servers from external datacenter #28
Labels
Comments
tomwganem
added a commit
to tomwganem/consul-helm
that referenced
this issue
Oct 19, 2018
tomwganem
added a commit
to tomwganem/consul-helm
that referenced
this issue
Nov 8, 2018
tomwganem
added a commit
to tomwganem/consul-helm
that referenced
this issue
Nov 28, 2018
tomwganem
added a commit
to tomwganem/consul-helm
that referenced
this issue
Feb 28, 2019
tomwganem
added a commit
to tomwganem/consul-helm
that referenced
this issue
Jul 31, 2019
|
This has been solved in Consul 1.8.0 with WAN Federation via mesh gateways. See https://www.consul.io/docs/k8s/installation/multi-cluster/overview for more details. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I want to connect a kubernetes consul cluster with another consul cluster in another datacenter over WAN, the communication only works one way, because this helm chart does not expose a route to the consul servers. So within the kubernetes cluster, I can resolve services that are running in the external datacenter. But if I'm in the external datacenter, I'm unable to resolve services that are running in the kubernetes cluster. The error given is
500 (rpc error: No path to datacenter)The text was updated successfully, but these errors were encountered: