luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Document Consul enterprise 1.10.0-1.10.4 forwards incompatibility with 1.11 (#11978) 

Also fixed a broken link in the 1.10.x upgrade instructions.

Co-authored-by: mrspanishviking <kcardenas@hashicorp.com>
This commit is contained in:
Matt Keeler 2022-01-10 17:18:40 -05:00 committed by GitHub
parent f9328bfdae
commit 9e788fbd47
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/upgrading/instructions/upgrade-to-1-10-x.mdx
View File

@ -14,7 +14,7 @@ description: >-
This guide explains how to best upgrade a single Consul Enterprise datacenter to v1.10.0 This guide explains how to best upgrade a single Consul Enterprise datacenter to v1.10.0
from a version of Consul that is forward compatible with v1.10. If you are on a major from a version of Consul that is forward compatible with v1.10. If you are on a major
version of Consul prior to 1.8, you will need to complete and [upgrade to 1.8.13](/docs/upgrading/instructions) version of Consul prior to 1.8, you will need to complete and [upgrade to 1.8.13](/docs/upgrading/instructions/upgrade-to-1-8-x)
or higher before continuing with this guide. If you are already on a major version of 1.8 or 1.9, then or higher before continuing with this guide. If you are already on a major version of 1.8 or 1.9, then
this guide will go over the procedures required for upgrading to v1.10. This process this guide will go over the procedures required for upgrading to v1.10. This process
will require intermediate version upgrades to a forward-compatible release of v1.8 or v1.9, will require intermediate version upgrades to a forward-compatible release of v1.8 or v1.9,

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

@ -16,6 +16,13 @@ upgrade flow.
## Consul 1.11.0 ## Consul 1.11.0
### 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.6 or higher to ensure forward compatibility and prevent
flapping of catalog registrations.
### Deprecated Agent Config Options ### Deprecated Agent Config Options
Consul 1.11.0 is compiled with Go 1.17 and now the ordering of Consul 1.11.0 is compiled with Go 1.17 and now the ordering of