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

[security] Upgrade to Envoy 1.14.2 #2579

Closed
pims opened this issue Jun 12, 2020 · 5 comments
Closed

[security] Upgrade to Envoy 1.14.2 #2579

pims opened this issue Jun 12, 2020 · 5 comments
Assignees
Labels
area/dependency Issues or PRs related to dependency changes. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action.
Milestone

Comments

@pims
Copy link
Contributor

pims commented Jun 12, 2020

Due to CVE https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11080 upgrading to Envoy 1.14.2 is recommended.

https://www.envoyproxy.io/docs/envoy/latest/version_history/v1.14.2

Happy to submit a PR if you’d like.

@pims pims changed the title [security] Upgrade to Envoy 1.4.2 [security] Upgrade to Envoy 1.14.2 Jun 12, 2020
@jpeach
Copy link
Contributor

jpeach commented Jun 13, 2020

Yup, there will be new security release soon. @pims if you would like to be the release manager for this, I'd be glad to shepherd that!

@pims
Copy link
Contributor Author

pims commented Jun 13, 2020

@jpeach I’d love to!

@jpeach
Copy link
Contributor

jpeach commented Jun 13, 2020 via email

@jpeach jpeach added the area/dependency Issues or PRs related to dependency changes. label Jun 15, 2020
@jpeach
Copy link
Contributor

jpeach commented Jun 15, 2020

Steps we need to do to make a 1.5.1 release:

  • Update the envoy image version on master
  • Update the envoy image version on the release-1.5 branch
  • Update hack/release/prepare-release.go to optionally take an OLDVERS NEWVERS arguments so that we can cut the 1.5.0 docs across to 1.5.1

Then we can:

  • cut the 1.5.1 tag
  • push the 1.5.1 Docker image
  • create and update GitHub release notes

Then, various docs updates (on master):

The release process is documented here, so if you find any inaccuracies we can correct them as we go.

@jpeach jpeach added the release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. label Jun 15, 2020
pims added a commit to pims/contour that referenced this issue Jun 15, 2020
jpeach pushed a commit that referenced this issue Jun 15, 2020
This updates #2579
Signed-off-by: tim <[email protected]>
pims added a commit to pims/contour that referenced this issue Jun 15, 2020
jpeach pushed a commit that referenced this issue Jun 17, 2020
@jpeach jpeach added this to the 1.5.1 milestone Jun 17, 2020
@pims
Copy link
Contributor Author

pims commented Jun 18, 2020

@pims pims closed this as completed Jun 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependency Issues or PRs related to dependency changes. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action.
Projects
None yet
Development

No branches or pull requests

2 participants