status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-10 22:06:20 +00:00
Code Issues Projects Releases Wiki Activity

Added info about Consul server config requirements

Browse Source
This commit is contained in:
boruszak 2022-08-08 15:09:12 -05:00
parent 017a94c0b6
commit 3ec5d8a9b1
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/content/docs/connect/cluster-peering/create-manage-peering.mdx
View File

@ -13,13 +13,19 @@ A peering token enables cluster peering between different datacenters. Once you
## Create a peering connection
To peer clusters, you must complete the following steps in order:
Cluster peering is not enabled by default on Consul servers. To peer clusters, you must first configure all Consul servers so that `peering` is `enabled`. For additional information, refer to [Configuration Files](/docs/agent/config/config-files).
Then, complete the following steps in order:
1. Create a peering token
1. Establish a connection between clusters
1. Export services between clusters
1. Authorize services for peers
### Enable peering on all Consul servers
Cluster peering is not enabled by default. To enable cluster peering,
### Create a peering token
You can generate peering tokens and initiate connections on any available agent using either the Consul UI or the API. If you use the API, we recommend performing these operations through a client agent in the partition you want to connect.