From a5a99c9d4a7b48093e1ccda90676824fba052c57 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Thu, 9 Feb 2023 04:04:33 -0600 Subject: [PATCH] docs: update Nomad 1.14 upgrade note to detail additonal info. (#16079) Co-authored-by: James Rasell --- website/content/docs/upgrading/upgrade-specific.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/docs/upgrading/upgrade-specific.mdx b/website/content/docs/upgrading/upgrade-specific.mdx index 910275b1fa..3998e7c325 100644 --- a/website/content/docs/upgrading/upgrade-specific.mdx +++ b/website/content/docs/upgrading/upgrade-specific.mdx @@ -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.