From a62cfd997bb72eb6543f618b4af0c8c1e3e20e32 Mon Sep 17 00:00:00 2001 From: cskh Date: Mon, 2 Oct 2023 19:12:15 -0400 Subject: [PATCH] docs: fix the description of meshgateway.mode=local in peering doc (#19042) docs: fix the description of meshgateway=local in peering doc --- .../k8s/connect/cluster-peering/usage/establish-peering.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/k8s/connect/cluster-peering/usage/establish-peering.mdx b/website/content/docs/k8s/connect/cluster-peering/usage/establish-peering.mdx index 375886132e..c784b57047 100644 --- a/website/content/docs/k8s/connect/cluster-peering/usage/establish-peering.mdx +++ b/website/content/docs/k8s/connect/cluster-peering/usage/establish-peering.mdx @@ -76,7 +76,7 @@ To use cluster peering with Consul on Kubernetes deployments, update the Helm ch ### Configure the mesh gateway mode for traffic between services -In Kubernetes deployments, you can configure mesh gateways to use `local` mode so that a service dialing a service in a remote peer dials the remote mesh gateway instead of the local mesh gateway. To configure the mesh gateway mode so that this traffic always leaves through the local mesh gateway, you can use the `ProxyDefaults` CRD. +In Kubernetes deployments, you can configure mesh gateways to use `local` mode so that a service dialing a service in a remote peer dials the local mesh gateway instead of the remote mesh gateway. To configure the mesh gateway mode so that this traffic always leaves through the local mesh gateway, you can use the `ProxyDefaults` CRD. 1. In `cluster-01` apply the following `ProxyDefaults` CRD to configure the mesh gateway mode.