From 2f8939efc8c4e75fbd3b374574ca5823227a20fb Mon Sep 17 00:00:00 2001 From: Michael Hofer Date: Mon, 8 May 2023 21:19:23 +0200 Subject: [PATCH] docs: extend peering-via-mesh-gateways intro (thanks @trujillo-adam) --- .../gateways/mesh-gateway/peering-via-mesh-gateways.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/website/content/docs/connect/gateways/mesh-gateway/peering-via-mesh-gateways.mdx b/website/content/docs/connect/gateways/mesh-gateway/peering-via-mesh-gateways.mdx index 2b0a1068364a..e5643c74f431 100644 --- a/website/content/docs/connect/gateways/mesh-gateway/peering-via-mesh-gateways.mdx +++ b/website/content/docs/connect/gateways/mesh-gateway/peering-via-mesh-gateways.mdx @@ -7,9 +7,7 @@ description: >- # Enabling Peering Control Plane Traffic -In addition to [service-to-service traffic routing](/consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-partitions), -we recommend routing control plane traffic between cluster peers through mesh gateways -to simplfy networking requirements. +This topic describes how to configure a mesh gateway to route control plane traffic between Consul clusters that share a peer connection. For information about routing service traffic between cluster peers through a mesh gateway, refer to [Enabling Service-to-service Traffic Across Admin Partitions](/consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-partitions). Control plane traffic between cluster peers includes the initial secret handshake and the bi-directional stream replicating peering data.