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: get k8s CI version markers from k8s infra bucket #98836
kubeadm: get k8s CI version markers from k8s infra bucket #98836
Conversation
Updates kubeadm version resolution to use kubernetes community infra bucket to fetch appropriate k8s ci versions. The images are already being pulled from the kubernetes community infra bucket meaning that a mismatch can occur when the ci version is fetched from the google infra bucket and the image is not yet present on k8s infra. Follow-up to kubernetes#97087 Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
The k8s release bucket constant is not longer overriden in network tests because the fetcher is mocked rather than using httptest.NewServer. See previous implementation in https://github.com/kubernetes/kubernetes/pull/49119/files#diff-82f2b09991047d4a1884d53dedadd64a473d5c4dc75293514e71773ceedf08e2R128 Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
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.
SGTM, if we are applying this it also must be backported in the support skew.
@hasheddan are you willing to send the cherry picks?
/lgtm
/approve
/triage accepted |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hasheddan, 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 |
@neolit123 absolutely :) |
/retest |
IIRC a release note must be added here, which will make it not required on the cherry picks.
|
/retest |
Thanks Dan! |
…836-upstream-release-1.19 Automated cherry pick of #98836: kubeadm: get k8s CI version markers from k8s infra bucket
…836-upstream-release-1.20 Automated cherry pick of #98836: kubeadm: get k8s CI version markers from k8s infra bucket
…836-upstream-release-1.18 Automated cherry pick of #98836: kubeadm: get k8s CI version markers from k8s infra bucket
What type of PR is this?
/kind bug
What this PR does / why we need it:
Updates kubeadm version resolution to use kubernetes community infra
bucket to fetch appropriate k8s ci versions. The images are already
being pulled from the kubernetes community infra bucket meaning that a
mismatch can occur when the ci version is fetched from the google infra
bucket and the image is not yet present on k8s infra.
Follow-up to #97087
Signed-off-by: hasheddan georgedanielmangum@gmail.com
Which issue(s) this PR fixes:
xref #98646
Special notes for your reviewer:
This should likely be CP'ed back to 1.20 branch as well.
Context: https://kubernetes.slack.com/archives/C09QZ4DQB/p1612269558032700
/priority critical-urgent
/sig release
/assign @neolit123
/cc @justaugustus @saschagrunert
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: