Backport of docs: add nomad incompatibility to 1.14 docs into release/1.14.x #15419
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #15397 to be assessed for backporting due to the inclusion of the label type/docs-cherrypick.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
See hashicorp/nomad#15266 for details.
I plan to submit a followup PR to update these docs once Nomad releases a fix. At that point Nomad users will still need to be informed that they must upgrade Nomad to a compatible version before upgrading Consul to 1.14.
Feel free to edit the wording or formatting or whatever. I just want to get any warning up for Nomad users ASAP so they don't discover this after having upgraded their Consul cluster and end up in a really bad state.
Overview of commits