From feb3bc2d2db7d174c3c278cfaa390142b9502768 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Thu, 10 Nov 2022 10:32:55 -0500 Subject: [PATCH] backport of commit ba7fa19507baa24cc832da9e045d9bf244bfb644 (#15324) This pull request was automerged via backport-assistant --- 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 57e7733764..4d18a48f11 100644 --- a/website/content/docs/upgrading/upgrade-specific.mdx +++ b/website/content/docs/upgrading/upgrade-specific.mdx @@ -18,7 +18,7 @@ upgrade flow. ### Service Mesh Compatibility -##### 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 @@ -36,6 +36,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