Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.11.x] Add support for Envoy 1.20.2 #12433

Merged
merged 3 commits into from
Feb 24, 2022
Merged

Conversation

eculver
Copy link
Contributor

@eculver eculver commented Feb 24, 2022

This updates our Envoy integration test matrix to include 1.20.2. The only notable change that was needed was to match against the Envoy version string which is:

4aaf9593152c6996b9da384c8918e9ad4f0abd4d/1.20.2-dev/Clean/RELEASE/BoringSSL

Note the -dev suffix.

This little version issue causes all the tests that use the assert_envoy_version helper to fail. To work around it, I just temporarily re-write the ENVOY_VERSION variable to include the suffix.

All other integration tests passed.

FUN FACT: The latest releases for Envoy 1.19 and 1.18 also have this -dev suffix that we'll need to deal with as well.

@eculver eculver requested a review from a team February 24, 2022 04:19
@github-actions github-actions bot added theme/envoy/xds Related to Envoy support type/ci Relating to continuous integration (CI) tooling for testing or releases labels Feb 24, 2022
@vercel vercel bot temporarily deployed to Preview – consul February 24, 2022 04:23 Inactive
@vercel vercel bot temporarily deployed to Preview – consul-ui-staging February 24, 2022 04:23 Inactive
@eculver eculver changed the title Add support for Envoy 1.20.2 [1.10.x] Add support for Envoy 1.20.2 Feb 24, 2022
@eculver eculver changed the title [1.10.x] Add support for Envoy 1.20.2 [1.11.x] Add support for Envoy 1.20.2 Feb 24, 2022
@kisunji
Copy link
Contributor

kisunji commented Feb 24, 2022

Tracking envoyproxy/envoy#20098 for this version issue

Looks like it was ACK'ed, but unsure if we want to wait for versions to be fixed or just push ahead with -dev

@eculver eculver added the pr/no-changelog PR does not need a corresponding .changelog entry label Feb 24, 2022
@eculver
Copy link
Contributor Author

eculver commented Feb 24, 2022

FYI - I'm applying the pr/no-changelog label because there appears to be a bug in the checker that is causing it to fail despite me having a changelog for this PR. I think it expects the entry to appear elsewhere.

@eculver eculver merged commit bd5ffe0 into release/1.11.x Feb 24, 2022
@eculver eculver deleted the eculver/1.11/envoy-1.20 branch February 24, 2022 23:23
@hc-github-team-consul-core
Copy link
Collaborator

🍒 If backport labels were added before merging, cherry-picking will start automatically.

To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/596009.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-changelog PR does not need a corresponding .changelog entry theme/envoy/xds Related to Envoy support type/ci Relating to continuous integration (CI) tooling for testing or releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants