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

Co-authored-by: James Rasell <jrasell@hashicorp.com>
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
This commit is contained in:
Dan Upton 2023-01-26 17:30:21 +00:00 committed by GitHub
parent 0edebe6e58
commit eb971cb507
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

@ -99,10 +99,10 @@ A breaking change was made in Consul 1.14 that:
- [Consul Connect is enabled by default.](/consul/docs/connect) - [Consul Connect is enabled by default.](/consul/docs/connect)
To disable, set [`connect.enabled`](/consul/docs/agent/config/config-files#connect_enabled) to `false`. To disable, set [`connect.enabled`](/consul/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 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.2 or earlier, do not upgrade to Consul 1.14 until earlier. If you operate Consul service mesh using Nomad 1.4.3 or earlier, do not upgrade to
[hashicorp/nomad#15266](https://github.com/hashicorp/nomad/issues/15266) is Consul 1.14 until [hashicorp/nomad#15266](https://github.com/hashicorp/nomad/issues/15266) and
fixed. [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 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. to use TLS for contacting the HTTP API, it will also incorrectly enable TLS for gRPC.