-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[2.11 branch] Upgrade to Kubernetes 1.15.11 #5578
[2.11 branch] Upgrade to Kubernetes 1.15.11 #5578
Conversation
/assign @mattymo |
fa5c005
to
3df6e45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We usually don't backport further than N-1 but this looks basic enough that I don't see a downside.
I've checked all the checksums, and it looks good.
/lgtm
/approve
Right, ... I don't have |
:D well.. Do we really plan on releasing a 2.11.1 ? I can close this one and focus on 2.13 anyway.. |
@mattymo what do you think ? |
@floryut can you rebase this to fix the docker repo issue? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, mattymo, Miouge1 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Upgrade to Kubernetes 1.5.11
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?: