From d4261c30c5e6d76d8a7b05f608282438f590fbdf Mon Sep 17 00:00:00 2001
From: Derek Menteer <105233703+hashi-derek@users.noreply.github.com>
Date: Thu, 10 Nov 2022 09:32:31 -0600
Subject: [PATCH] Add peering incompatibility warning to upgrade docs. (#15319)

---
 website/content/docs/upgrading/upgrade-specific.mdx | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/website/content/docs/upgrading/upgrade-specific.mdx b/website/content/docs/upgrading/upgrade-specific.mdx
index 109600626..65b40e358 100644
--- a/website/content/docs/upgrading/upgrade-specific.mdx
+++ b/website/content/docs/upgrading/upgrade-specific.mdx
@@ -24,7 +24,7 @@ A breaking change was made in Consul 1.14 that:
 - [Consul Connect is enabled by default.](/docs/connect) To disable, set
 [`connect.enabled`](/docs/agent/config/config-files#connect_enabled) to `false`.
 
-##### Changes to gRPC TLS configuration
+#### Changes to gRPC TLS configuration
 
 **Make configuration changes** if using sidecar proxies or gateways that include any of the following configuration file values:
 1. [`ports.https`](/docs/agent/config/config-files#https_port) - Encrypts gRPC in Consul 1.12 and prior
@@ -43,6 +43,14 @@ For most environments, the Envoy communication to Consul is loop-back only and d
 
 If you already use gRPC encryption, change the existing `ports.grpc` to `ports.grpc_tls` in your configuration to ensure compatibility with future releases.
 
+#### Changes to peering
+
+[Cluster peering](/docs/connect/cluster-peering) was released in Consul 1.13 as an experimental feature.
+In Consul 1.14, cluster peering has been improved and is now considered stable. All experimental peering
+connections created by 1.13 should be
+[deleted](/docs/connect/cluster-peering/create-manage-peering#delete-peering-connections)
+prior to upgrading, as they will no longer be compatible with 1.14.
+
 ## Consul 1.13.x
 
 ### Service Mesh Compatibility