status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-10 22:06:20 +00:00
Code Issues Projects Releases Wiki Activity

Clean up placeholder diagrams, rename file to use dashes

Browse Source
This commit is contained in:
Preetha Appan 2020-05-12 16:34:59 -05:00
parent c32de785a0
commit 8ce0a2509b
2 changed files with 5 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/data/docs-navigation.js
View File

@ -155,7 +155,7 @@ export default [
content: ['envoy', 'built-in', 'integrate'],
},
'mesh_gateway',
'wan_federation_via_mesh_gateways',
'wan-federation-via-mesh-gateways',
{
category: 'registration',
content: ['service-registration', 'sidecar-service'],

40
website/pages/docs/connect/wan_federation_via_mesh_gateways.mdx → website/pages/docs/connect/wan-federation-via-mesh-gateways.mdx
View File

@ -21,6 +21,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.
If you are using Kubernetes, refer to our [Kubernetes Multi Cluster](/docs/k8s/installation/multi-cluster) documentation.
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
@ -54,21 +56,6 @@ the gulf between disparate Consul datacenters:
over `8300/tcp`. Several distinct kinds of messages can be received on this
port, such as RPC requests forwarded from servers in other datacenters.
TODO(wanfed): <NORMAL-DIAGRAM>
[ name:server1/dc1 ] <----(wan-gossip )----> [ name:server3/dc2 ]
| lan: 10.0.0.1 | [ lan: 10.1.2.1 ]
[ wan: 37.4.5.7 ] <----(cross-dc RPC)----> [ wan: 54.6.7.9 ]
/\
||
(lan-gossip )
||
(RPC for dc2)
||
[ name:client9/dc1 ]
[ lan: 10.0.0.9 ]
In this network topology individual Consul client agents on a LAN in one
datacenter never need to directly dial servers in other datacenters. This
@ -81,26 +68,9 @@ to allow for services in the service mesh to freely connect between datacenters
regardless of the lateral connectivity of the nodes hosting the Consul client
agents.
By activating WAN federation via mesh gateways [TODO(wanfed):link] the servers
By activating WAN federation via mesh gateways the servers
can similarly use the existing mesh gateways to reach each other without
themeselves being directly reachable.
TODO(wanfed): <WANFED-DIAGRAM>
[ name:gateway1/dc1 ] <----(wan-gossip )----> [ name:gateway4/dc2 ]
| lan: 10.0.0.5 | [ lan: 10.1.2.5 ]
[ wan: 37.4.5.7 ] <----(cross-dc RPC)----> [ wan: 54.6.7.9 ]
/\ /\
|| ||
(wan-gossip ) (wan-gossip )
|| ||
(cross-dc RPC) (cross-dc RPC)
|| ||
\/ \/
[ name:server1/dc1 ] [ name: server3/dc2 ]
[ lan: 10.0.0.1 ] [ lan: 10.1.2.1 ]
themselves being directly reachable.
## Configuration
@ -112,8 +82,6 @@ these SAN fields:
server.<this_datacenter>.<domain> (normal)
<node_name>.server.<this_datacenter>.<domain> (needed for wan federation)
[TODO(wanfed):link]
This can be achieved using any number of tools, including `consul tls cert
create` with the `-node` flag.