I have successfully established peering between two Consul datacenters running in separate kubernetes clusters.
Peering is okay, I can export services from one or the other and it shows up as green in the UI. I have not enabled ACLs.
But I cannot resolve anything between the datacenters, not by DNS or query via the API.
The API gives an error saying: “No path to datacenter” and if i turn on debug logging on the server side i get this error as well: "agent.dns: error processing discovery query: error=“no path to datacenter” and for querying via the API: “RPC request for DC is currently failing as no path was found”.
The helm chart is configured with service exposure true through loadbalancer.
I have configured peerThroughMeshGateways=true via the Mesh kind.
If I query the api for peers it does not list IP addresses of dc2 from dc1, but if I query peers in dc2 it lists ip addresses for dc1. But the error for no path to datacenter is the same when querying from both sides.
Hi @johanlundberg92 ,
Could you please share the DNS query you are using? Please note that your DNS queries should be in either of the forms below.
<service-name>.service.<peer-name>.peer.<domain><service-name>.virtual.<peer-name>.<domain>