github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

docs: fix the description of meshgateway.mode=local in peering doc (#19042) 

docs: fix the description of meshgateway=local in peering doc
pull/19052/head
cskh 1 year ago committed by GitHub
parent
21ea527089
commit
a62cfd997b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      website/content/docs/k8s/connect/cluster-peering/usage/establish-peering.mdx

2
website/content/docs/k8s/connect/cluster-peering/usage/establish-peering.mdx
Unescape View File

@ -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 ### 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. 1. In `cluster-01` apply the following `ProxyDefaults` CRD to configure the mesh gateway mode.

Write Preview
Loading…
Cancel
Save