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 #14813 from hashicorp/docs/1-10-upgrade-compatibility-clarification 

docs: clarify 1.10 upgrade compatibility
This commit is contained in:
Jared Kirschner 2022-10-21 16:57:23 -04:00 committed by GitHub
parent 0a5b238ca8 db413fcdb8
commit cc843c4be8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/content/docs/upgrading/upgrade-specific.mdx
View File

@ -264,9 +264,10 @@ be replaced with the new [`tls` stanza](/docs/agent/config/config-files#tls-conf
### 1.10 Compatibility <EnterpriseAlert inline />
Consul Enterprise versions 1.10.0 through 1.10.4 contain a latent bug that
causes those client or server agents to deregister their own services or health
checks when some of the servers have been upgraded to 1.11. Before upgrading Consul Enterprise servers to 1.11, all Consul agents should first
be upgraded to 1.10.7 or higher to ensure forward compatibility and prevent
flapping of catalog registrations.
checks when some of the servers have been upgraded to 1.11 or later.
Before upgrading Consul Enterprise servers to 1.11 or later,
you should first upgrade all Consul client and server agents to 1.10.7 or higher
to ensure forward compatibility and prevent flapping of catalog registrations.
### Deprecated Agent Config Options