Merge pull request #12101 from hashicorp/wan-federation-with-mesh-gateways-networking-visual

docs: show WAN fed with/without mesh gateways
This commit is contained in:
Jared Kirschner 2022-01-18 09:22:13 -05:00 committed by GitHub
commit 39f00317c4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 3919 additions and 1 deletions

View File

@ -20,6 +20,8 @@ Consul cluster, operators must ensure that all Consul servers in every
datacenter must be directly connectable over their WAN-advertised network
address from each other.
[![WAN federation without mesh gateways](/img/wan-federation-connectivity-traditional.png)](/img/wan-federation-connectivity-traditional.png)
This requires that operators setting up the virtual machines or containers
hosting the servers take additional steps to ensure the necessary routing and
firewall rules are in place to allow the servers to speak to each other over
@ -38,7 +40,7 @@ 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)
[![WAN federation with mesh gateways](/img/wan-federation-connectivity-mesh-gateways.png)](/img/wan-federation-connectivity-mesh-gateways.png)
## Architecture

BIN
website/public/img/wan-federation-connectivity-mesh-gateways.png (Stored with Git LFS) Executable file

Binary file not shown.

File diff suppressed because it is too large Load Diff

After

Width:  |  Height:  |  Size: 185 KiB

BIN
website/public/img/wan-federation-connectivity-traditional.png (Stored with Git LFS) Executable file

Binary file not shown.

File diff suppressed because it is too large Load Diff

After

Width:  |  Height:  |  Size: 124 KiB