From 50e40ecc14c55f3a6c6221c62277eacfc30b561b Mon Sep 17 00:00:00 2001 From: Luiz Aoqui Date: Tue, 30 May 2023 11:38:57 -0400 Subject: [PATCH 1/2] docs: add note about Nomad support for Consul 1.13.8 --- website/content/docs/upgrading/upgrade-specific.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/content/docs/upgrading/upgrade-specific.mdx b/website/content/docs/upgrading/upgrade-specific.mdx index 62e466d6687..5ed62dadd17 100644 --- a/website/content/docs/upgrading/upgrade-specific.mdx +++ b/website/content/docs/upgrading/upgrade-specific.mdx @@ -402,6 +402,12 @@ if the Vault policy is not modified as described. As a precaution, we recommend both modifying the Vault policy and upgrading to Consul 1.13.3 or later to avoid the breaking nature of that change. +### Nomad Incompatibility + +Nomad users should not upgrade to Consul 1.13.8 as an API change in Consul +prevents Nomad from correctly detecting the Consul agent version, resulting in +allocations not being placed in those clients. + ## Consul 1.12.x ((#consul-1-12-0)) ### Modify Vault Policy for Vault CA Provider From 34adca3a8080a5985786ccdad50c8b12a04eeb46 Mon Sep 17 00:00:00 2001 From: Luiz Aoqui Date: Thu, 1 Jun 2023 16:46:01 -0400 Subject: [PATCH 2/2] apply code review changes --- website/content/docs/upgrading/upgrade-specific.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/content/docs/upgrading/upgrade-specific.mdx b/website/content/docs/upgrading/upgrade-specific.mdx index 5ed62dadd17..985a7033532 100644 --- a/website/content/docs/upgrading/upgrade-specific.mdx +++ b/website/content/docs/upgrading/upgrade-specific.mdx @@ -28,7 +28,7 @@ Before upgrading, ensure that all of your applications can handle this new API b #### Remove deprecated service-defaults peer upstream override behavior -When configuring a service defaults configuration entry, the [`UpstreamConfig.Overrides` configuration](/consul/docs/connect/config-entries/service-defaults#upstreamconfig-overrides) +When configuring a service defaults configuration entry, the [`UpstreamConfig.Overrides` configuration](/consul/docs/connect/config-entries/service-defaults#upstreamconfig-overrides) does not apply to peer upstreams unless the [`Peer`](/consul/docs/connect/config-entries/service-defaults#upstreamconfig-overrides-peer) field is explicitly provided. This change removes the backward-compatibility behavior introduced in Consul 1.15.x. Refer to the [upgrade instructions for 1.15.x](#service-defaults-overrides-for-upstream-peered-services) for more information. @@ -152,7 +152,7 @@ In Consul v1.15 and higher: UpstreamConfig = { Overrides = [ { - Name = foo # Applies to local service `foo` + Name = foo # Applies to local service `foo` }, { Name = foo # Applies to `foo` imported from peered cluster `bar` @@ -404,9 +404,9 @@ to Consul 1.13.3 or later to avoid the breaking nature of that change. ### Nomad Incompatibility -Nomad users should not upgrade to Consul 1.13.8 as an API change in Consul -prevents Nomad from correctly detecting the Consul agent version, resulting in -allocations not being placed in those clients. +Nomad users should not upgrade to Consul v1.13.8. An API change in this Consul +release prevents Nomad from correctly detecting the Consul agent version. As a +result, allocations are not placed in clients running v1.13.8. ## Consul 1.12.x ((#consul-1-12-0))