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
kubeadm: update the version constants for 1.16 #80833
Conversation
/hold |
- common_test.go: use constants.CurrentKubernetesVersion - diff_test.go: write temporary files instead of using testdata. this allows us to not have to bump kubernetesVersions in the testdata files (now removed) - policy_test.go: apply fixes to tests that were previously passing, but a bump in constants.go breaks them. these tests now work for any version.
9c3d80b
to
8aa69ea
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.
@neolit123 thanks for this fix!
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, neolit123 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 |
/hold cancel |
/retest Review the full test history for this PR. Silence the bot with an |
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.
Thanks!
LGTM
What this PR does / why we need it:
commit description has details.
this is still an issue:
kubernetes/kubeadm#1260
we are defaulting ClusterConfiguration with a version that resolves a label from the internet and this is such a can of worms.
unit tests wrongly end up calling:
https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/util/config/common.go#L91
and if the bumped minimal CP version in constants.go is newer than the latest stable version from the label we use, this can end up in:
in a large number of unit tests...
Which issue(s) this PR fixes:
xref kubernetes/kubeadm#1260
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/assign @fabriziopandini @rosti
/cc @yagonobre
/priority critical-urgent
/kind cleanup