Service exposed in a wan federated + cluster peering scenario

Hi all,

I have some clusters using wan federated and I want to start using the new cluster peering mechanism for new sites.

I setup a test environment with three clusters to simulate our current structure:

  1. dc1 - Primary datacenter
  2. dc2 - Secondary datacenter (WAN federated with dc1)
  3. dc3 - Peered cluster with both dc1 and dc2

Results:

  • Services from dc3 were exposed to both dc1 and dc2.
  • Services from dc1 (primary datacenter) were successfully exposed to the peered cluster dc3.
  • However, services from dc2 (secondary datacenter) were not exposed to the peered cluster dc3.

From my understanding, it seems that it’s not possible to export services from a secondary WAN-federated datacenter (like dc2) to a peered cluster (like dc3), while services from the primary datacenter (dc1) are successfully exposed to the peered cluster. I found a related section in the Consul code: consul/agent/consul/config_endpoint.go at main · hashicorp/consul · GitHub.

Question: Is there any way to export services from a secondary WAN-federated datacenter to a peered cluster, or is this a known limitation? Are there any workarounds to allow service exposure from dc2 to dc3?

Any help or guidance would be greatly appreciated!

2 Likes