Consul datacenter federation enables operators to extend their Consul environments by connecting
multiple HashiCorp Cloud Platform (HCP) Consul clusters together within a region.
This process ultimately lowers the operational overhead of connecting applications across distinct regions, as well as enables a more consistent, and improved, security model. With HCP Consul, the server-to-server connectivity is automatically handled by the HCP platform.
To learn how to enable HCP Consul federation, please visit the Federate Multiple HCP Consul clusters tutorial.
- Do not overlap network CIDR blocks for the HashiCorp Virtual Network (HVN) associated with the federated Consul Clusters.
- Consul has the concept of primary and secondary clusters. Any cluster that you intend to designate as secondary must be added through federation. Standalone clusters cannot be added to an existing fedearation.
- By default, the total number of Consul clusters allowed in an HCP Organization is limited to 3 (soft limit). If you would like to federate additional clusters, please file a support ticket to increase the limit.
- For clusters federated across regions, all the Consul clusters in the federation must be Plus tier for production deployments.
- All clusters that are part of the federation must be in the same tier. Please refer to the table below for details on HCP Consul tiers.
- Production clusters with federation must all be of the Plus tier.
- The table below shows the federation options for different HCP Consul Tiers.
|Development (For proof of concept testing only)||Intra and Inter region federation|
|Standard (For production deployments)||Intra region federation|
|Plus (For production deployments)||Intra* and Inter region federation|
*Must be with another Plus tier cluster