Backport of [NET-5622] build: consolidate Envoy version management into release/1.19.x #21521
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 #21245 to be assessed for backporting due to the inclusion of the label backport/1.19.
🚨
The person who merged in the original PR is:
@sarahalsmiller
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
Description
Consolidate Envoy versions into a single canonical file to enable simpler management and avoid missed updates in the future.
This effort is motivated by repeated experience struggling to ensure that we updated Envoy "everywhere" we needed to. Even moreso than managing our Go versions, there's a significant amount of sprawl when it comes to Envoy, and addressing that will enable us to more confidently update versions as well as automate the toil of doing so when new releases are available.
I've opened manual backports through 1.15 Ent to ensure that the
ENVOY_VERSIONS
file is available on all actively tested branches; this is necessary for sourcing in nightly integration tests onmain
, so required for this PR prior to merge.This change also includes:
I have not removed or changed defunct uses of Envoy in Windows integration tests as I think that would be best accomplished as a separate holistic Windows cleanup PR.
Testing & Reproduction steps
get-envoy-versions
output matches filemain
versions match expectedLocal agent test:
main
PR branch
Follow-ups
Links
Manual backport PRs:
PR Checklist
Overview of commits