generated from hashicorp/terraform-provider-scaffolding
-
Notifications
You must be signed in to change notification settings - Fork 50
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0055a8e
commit 1143722
Showing
1 changed file
with
5 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,14 @@ | ||
--- | ||
subcategory: "" | ||
page_title: "Federate HCP Consul clusters - HCP Provider" | ||
page_title: "Federation with Auto HVN Peering - HCP Provider" | ||
description: |- | ||
An example of federating a new HCP Consul cluster with an existing one. | ||
An example of federating a new HCP Consul cluster with an existing one via auto peering. | ||
--- | ||
|
||
# Federate a new HCP Consul cluster with an existing one | ||
# Federation with Auto HVN Peering | ||
|
||
Once you have a HCP Consul cluster, you can create a new Consul cluster to federate with the existing one. | ||
By providing `auto_hvn_to_hvn_peering` as a parameter on the secondary cluster, the HVNs are being peered | ||
automatically ensuring full connectivity. This parameter only ever has to be provided on secondary clusters. | ||
|
||
{{ tffile "examples/guides/consul_cluster_federation/main.tf" }} |