Getting started with mesh gateway issues

[mister2d]

@lkysow After tackling it some more today I was able to get it to work with this solution:

Mesh Gateway federation woes!

@karl-cardenas-coding I was able to figure it out. primary_gateways was set to the Pod’s service IP which was not routable to the other cluster. I had to set the wanAddress to a static value which reflected the FQDN of the wan interface. Only then did the clusters actually sync completely. When running a consul members -wan, all server nodes now report “alive” status. Working helm values DC1: global: datacenter: dc1 name: consul domain: consul tls: enabled: true …

I hope it’s ideal.