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

docs: update Nomad 1.14 upgrade note to detail additonal info. (#16079) 

Co-authored-by: James Rasell <jrasell@hashicorp.com>
backport/patch-1/legally-massive-flounder
hc-github-team-consul-core 2023-02-09 04:04:33 -06:00 committed by GitHub
parent faaa2c11f0
commit a5a99c9d4a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -26,10 +26,10 @@ 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`.
The changes to Consul service mesh in version 1.14 are incompatible with Nomad 1.4.2 and
earlier. If you operate Consul service mesh using Nomad 1.4.2 or earlier, do not upgrade to Consul 1.14 until
[hashicorp/nomad#15266](https://github.com/hashicorp/nomad/issues/15266) is
fixed.
The changes to Consul service mesh in version 1.14 are incompatible with Nomad 1.4.3 and
earlier. If you operate Consul service mesh using Nomad 1.4.3 or earlier, do not upgrade to
Consul 1.14 until [hashicorp/nomad#15266](https://github.com/hashicorp/nomad/issues/15266) and
[hashicorp/nomad#15360](https://github.com/hashicorp/nomad/issues/15360) have been fixed.
For 1.14.0, there is a known issue with `consul connect envoy`. If the command is configured
to use TLS for contacting the HTTP API, it will also incorrectly enable TLS for gRPC.