Merge pull request #14154 from hashicorp/1.13.1-upgrade-considerations

website/content/docs/upgrading/instructions/index.mdx

@@ -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
 

website/content/docs/upgrading/upgrade-specific.mdx

@@ -14,7 +14,20 @@ provided for their upgrades as a result of new features or changed behavior.
 This page is used to document those details separately from the standard
 upgrade flow.
 
-## Consul 1.13.0
+## 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.
+
+This bug is fixed in Consul versions 1.13.1 and newer.
 
 ### gRPC TLS