diff --git a/website/content/docs/connect/gateways/mesh-gateway/index.mdx b/website/content/docs/connect/gateways/mesh-gateway/index.mdx index 2622a06760..dd747c5c99 100644 --- a/website/content/docs/connect/gateways/mesh-gateway/index.mdx +++ b/website/content/docs/connect/gateways/mesh-gateway/index.mdx @@ -61,7 +61,8 @@ receive incoming traffic even if that traffic has passed through a gateway. ## Modes of Operation Each upstream of a Connect proxy can be configured to be routed through a mesh gateway. Depending on -your network, the proxy's connection to the gateway can happen in one of the following modes: +your network, the proxy's connection to the gateway can happen in one of the following modes +illustrated in the diagram above: - `local` - In this mode the Connect proxy makes its outbound connection to a gateway running in the same datacenter. That gateway is then responsible for ensuring the data gets forwarded along to diff --git a/website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx b/website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx index e892c81622..eca396d927 100644 --- a/website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx +++ b/website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx @@ -38,6 +38,8 @@ Operators looking to simplify their WAN deployment and minimize the exposed security surface area can elect to join these datacenters together using [mesh gateways](/docs/connect/gateways/mesh-gateway) to do so. +![Mesh Gateway Architecture](/img/mesh-gateways.png) + ## Architecture There are two main kinds of communication that occur over the WAN link spanning diff --git a/website/public/img/mesh-gateways.png b/website/public/img/mesh-gateways.png index b7858c692e..3b179619b4 100644 Binary files a/website/public/img/mesh-gateways.png and b/website/public/img/mesh-gateways.png differ diff --git a/website/public/img/mesh-gateways.svg b/website/public/img/mesh-gateways.svg new file mode 100755 index 0000000000..eccf660c0d --- /dev/null +++ b/website/public/img/mesh-gateways.svg @@ -0,0 +1,1671 @@ + + + + + + + + + + + + + + + + + + + DC1 + + + + | ON PREMISES + DC2 + + + + | CLOUD US-EAST-1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LEADER + + + + LEADER + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + B + SERVICE + + + + A + SERVICE + + Cross-DC Communication (WAN Federation) Models + + + + + + MeshGateway.Mode = "none" + connect.enable_mesh_gateway_wan_federation=false + connect.enable_mesh_gateway_wan_federation=true + MeshGateway.Mode = "remote" + MeshGateway.Mode = "local" + System Components + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LEADER + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A + SERVICE + Service Instance + Sidecar Proxy (Envoy) + Mesh Gateway + Consul Client Agent + Consul Server Agents + not shown: the Consul client agentdeployed with each gatewayto manage its configuration + + + + Cross-DCCommunication Paths + Data Plane + + + Control Plane + see Consul agent config option:connect.enable_mesh_gateway_wan_federation + see "MeshGateway.Mode" config option in:(1) service proxy upstream, (2) service proxy,(3) service-defaults, (4) proxy-defaults + + + + + CONSUL SERVICE MESH +