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

Upgrade to nginx-ingress-controller 0.29.0 #30

Merged
merged 1 commit into from
Feb 18, 2020
Merged

Upgrade to nginx-ingress-controller 0.29.0 #30

merged 1 commit into from
Feb 18, 2020

Conversation

sslavic
Copy link

@sslavic sslavic commented Feb 17, 2020

nginx IC 0.29.0 was updated from 1.13.1 to most recent go 1.13.8 which among other things includes fixes hardening certificate validation in go's crypto/x509 package (done in Go 1.13.7), which should help nginx IC panic less i.e. better handle (survive) invalid certificates customers configure as in https://github.com/giantswarm/giantswarm/issues/8707

For complete nginx IC 0.29.0 change log see https://github.com/kubernetes/ingress-nginx/blob/master/Changelog.md#0290
Go 1.13 release notes can be found at https://golang.org/doc/devel/release.html#go1.13

Plan is to release this as 1.5.0 and include it in legacy WIP releases:

@sslavic sslavic requested review from a team February 17, 2020 22:31
@sslavic sslavic self-assigned this Feb 17, 2020
Copy link
Contributor

@corest corest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@sslavic sslavic merged commit 2c9e2bb into master Feb 18, 2020
@sslavic sslavic deleted the nginx-0.29.0 branch February 18, 2020 10:43
@cokiengchiara
Copy link
Contributor

cokiengchiara commented Feb 18, 2020

@sslavic

latest nginx ic in kvm 11.1.0 is 1.1.1... so we include all changes from 1.2.0, 1.2.1, 1.3.0, and 1.5.0? Same w Azure and AWS?

@sslavic
Copy link
Author

sslavic commented Feb 18, 2020

Yes, 1.4.0 too.

@cokiengchiara
Copy link
Contributor

Yes, 1.4.0 too.

Ah right. So I will draft the paragraph release notes for that.

Can we create releases with only these changes, so no coordination w other teams needed?

@sslavic
Copy link
Author

sslavic commented Feb 18, 2020

Yes, this is exactly what we're doing with giantswarm/releases#89

AFAIK my answer to your previous related question there still holds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants