status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #15032 from hashicorp/docs/mgw-primary-upgrade

This commit is contained in:
Freddy 2022-10-21 16:52:27 -06:00 committed by GitHub
parent cc843c4be8 72553b3499
commit ccf15f4153
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx
View File

@ -184,3 +184,18 @@ expected result:
- Ensure any API request that activates datacenter request forwarding. such as
[`/v1/catalog/services?dc=<OTHER_DATACENTER_NAME>`](/api-docs/catalog#dc-1)
succeeds.
### Upgrading the primary gateways
Once federation is established, secondary datacenters will continuously request
updated mesh gateway addresses from the primary datacenter. Consul routes the requests
through the primary datacenter's mesh gateways. This is because
secondary datacenters cannot directly dial the primary datacenter's Consul servers.
If the primary gateways are upgraded, and their previous instances are decommissioned
before the updates are propagated, then the primary datacenter will become unreachable.
To safely upgrade primary gateways, we recommend that you apply one of the following policies:
- Avoid decommissioning primary gateway IP addresses. This is because the [primary_gateways](/docs/agent/config/config-files#primary_gateways) addresses configured on the secondary servers act as a fallback mechanism for re-establishing connectivity to the primary.
- Verify that addresses of the new mesh gateways in the primary were propagated
to the secondary datacenters before decommissioning the old mesh gateways in the primary.