Update with more details on 1.13.0 issue

This commit is contained in:
Tu Nguyen 2022-08-11 14:43:27 -07:00
parent 089a9c6e59
commit db936a3412
2 changed files with 12 additions and 9 deletions

View File

@ -13,12 +13,14 @@ This document is intended to help users who find themselves many versions behind
## Upgrade Path
Our recommended upgrade path is to move through the following sequence of versions:
- 0.8.5 (final 0.8.x)
- 1.2.4 (final 1.2.x)
- 1.6.10 (final 1.6.x)
- 1.8.19 (final 1.8.x)
- Latest 1.10.x
- Latest current version (1.11.x or 1.12.x)
- Latest 1.12.x
- Latest 1.13.x ([at least 1.13.1](/docs/upgrading/upgrade-specific#service-mesh-compatibility))
## Getting Started
@ -28,9 +30,6 @@ The upgrade guides will mention notable changes and link to relevant changelogs
we recommend reviewing the changelog for versions between the one you are on and the
one you are upgrading to at each step to familiarize yourself with changes.
~> **Note:** If you are upgrading from `1.11`+ and have connect proxies
registered, upgrade directly to `1.13.1` instead of `1.13.0`.
Select your _currently installed_ release series:
- [1.9.x](/docs/upgrading/instructions/upgrade-to-1-10-x)
- [1.8.x](/docs/upgrading/instructions/upgrade-to-1-10-x)

View File

@ -17,12 +17,16 @@ upgrade flow.
## Consul 1.13.x
### Service Mesh Compatibility
Existing Consul deployments using service mesh (i.e., containing any registered Connect proxies)
should upgrade to **at least Consul 1.13.1**.
Consul 1.13.0 contains a bug that prevents Consul server agents from restoring saved state
on startup if the state (1) was generated before Consul 1.13 (such as during an upgrade),
and (2) contained any Connect proxy registrations.
Existing Consul deployments using service mesh (i.e., containing any registered
Connect proxies) should upgrade to **at least Consul 1.13.1**.
Consul 1.13.0 contains a bug that prevents Consul server agents from restoring
saved state on startup if the state
1. was generated before Consul 1.13 (such as during an upgrade), and
2. contained any Connect proxy registrations.
This bug is fixed in Consul versions 1.13.1 and newer.
### gRPC TLS