[1.10] docs: Correct Envoy support matrix #14334
Merged
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.
Description
Long ago, when I was first learning how our Envoy support matrix worked, I inadvertently backported support for Envoy 1.20 to Consul 1.10: #12434. Since this patch was related to a CVE, my guess is that we wanted to be able to give users an upgrade path to a patched Envoy. However, for Consul 1.10, they could do this with Envoy 1.18.6 as opposed to adding support for Envoy 1.20. Alas, this is the history and I cannot go back and change it.
With that said, we don't want to confuse users about our Envoy support matrix, so this resets our docs for 1.10 to what the expected support should be for Consul 1.10. These values are what should also be documented in the Consul 1.12 and 1.11 docs. There will be accompanying PRs for Consul 1.12 and 1.11 linked below.
In the end, all the docs linked below should have consistent Envoy versions for each release series.
Links