github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add peering incompatibility warning to upgrade docs.

pull/15319/head
Derek Menteer 2022-11-09 17:08:11 -06:00
parent b51f0e25e9
commit ba7fa19507
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

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