What is Cluster Peering?
You can create peering connections between two or more independent clusters so that services deployed to different partitions or datacenters can to communicate.
- Create a peering token to share with other clusters
- Make services available to other clusters
For detailed instructions on setting up cluster peering with the Consul CLI, refer to Create and Manage Peering Connections.
Regardless of whether you connect your clusters through WAN federation or cluster peering, human and machine users can use either method to discover services in other clusters or dial them through the service mesh.
Technical preview constraints
- Consul ACLs must be disabled or the ACL must be set to .
- Mesh gateways for server to server traffic are not available. However, mesh gateways for service to service traffic between clusters are available.
- Services exported to peered clusters must not be configured as HTTP.
- The command is not supported. To manage intentions that specify services in peered clusters, use configuration entries.
- are not supported.
- Configuring service failover across peers is not supported.
- Accessing key/value stores across peers is not supported.
- Non-enterprise Consul instances cannot sync services with namespaces outside of the namespace.