From c1f71e3ef82c5c0c121de10cf280f082a32599e2 Mon Sep 17 00:00:00 2001 From: boruszak Date: Tue, 4 Oct 2022 10:34:42 -0500 Subject: [PATCH] list --- .../connect/cluster-peering/create-manage-peering.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx index 1a6b682000..d410bfc613 100644 --- a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx +++ b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx @@ -123,9 +123,9 @@ If you need to re-establish a connection, you must generate a new peering token. 1. In the Consul UI for the datacenter associated with `cluster 02`, click **Peers** and then **Add peer connection**. -2. Click **Establish peering**. -3. In the **Name of peer** field, enter `cluster-01`. Then paste the peering token in the **Token** field. -4. Click **Add peer**. +1. Click **Establish peering**. +1. In the **Name of peer** field, enter `cluster-01`. Then paste the peering token in the **Token** field. +1. Click **Add peer**. @@ -377,7 +377,9 @@ Next to the name of the peer, click **More** (three horizontal dots) and then ** ## L7 traffic management between peers + The following sections describe how to enable L7 traffic management features between peered clusters. + ### Service resolvers for redirects and failover As of Consul v1.14, you can use [dynamic traffic management](/consul/docs/connect/l7-traffic) to configure your service mesh so that services automatically failover and redirect between peers. The following examples update the [`service-resolver` config entry](/docs/connect/config-entries/) in `cluster-01` so that Consul redirects traffic intended for the `frontend` service to a backup instance in peer `cluster-02` when it detects multiple connection failures.