Improve mesh gateway diagram
Diagram now shows all possible cross-DC communication models supported by mesh gateways for both the control and data planes.
This commit is contained in:
parent
0069c586df
commit
21753a9331
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
BIN
website/public/img/mesh-gateways.png (Stored with Git LFS)
BIN
website/public/img/mesh-gateways.png (Stored with Git LFS)
Binary file not shown.
File diff suppressed because it is too large
Load Diff
After Width: | Height: | Size: 135 KiB |
Loading…
Reference in New Issue