luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

docs: add note about Nomad support for Consul 1.13.8 (#17512) 

* docs: add note about Nomad support for Consul 1.13.8

* apply code review changes
This commit is contained in:
Luiz Aoqui 2023-06-01 18:09:21 -04:00 committed by GitHub
parent b068b41288
commit 054ba0349c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 2 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

@ -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`
@ -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 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))
### Modify Vault Policy for Vault CA Provider