-
Notifications
You must be signed in to change notification settings - Fork 123
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
k8s-1.33: Update url to check previous k8s version #1396
k8s-1.33: Update url to check previous k8s version #1396
Conversation
@@ -13,7 +13,7 @@ function getKubernetesClosestStableVersion() { | |||
kubernetes_minor_version=$(echo $kubernetes_version | cut -d. -f2) | |||
packages_major_version=$(echo $kubernetes_version | cut -d. -f1) | |||
packages_minor_version=$((kubernetes_minor_version-1)) | |||
packages_version="$(curl --fail -L "https://storage.googleapis.com/kubernetes-release/release/stable-${packages_major_version}.${packages_minor_version}.txt" | sed 's/^v//')" | |||
packages_version="$(curl --fail -L "https://raw.githubusercontent.com/kubevirt/kubevirtci/refs/heads/main/cluster-provision/k8s/1.${packages_minor_version}/version")" |
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.
I am not sure whether we should use ourselves as a source of truth around k8s release versions - is there no other way to determine the latest stable k8s version from any kubernetes release resource?
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.
I thought this would be a good solution as that is the latest known good version that we are testing with for the previous provider.
I wouldn't consider it a source of truth - in this case we just need some recent version to install the rpms - the binaries get replaced later anyway.
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.
I think I have found a better option.
The old URL used to check the previous kubernetes version no longer exists for versions greater than v1.31 - this is causing the provisioning of the k8s-1.33 provider to fail[1] Update to get the version from the kubevirtci repo itself. [1] https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_project-infra/4010/rehearsal-check-provision-k8s-1.33/1899779863519170560#1:build-log.txt%3A166 Signed-off-by: Brian Carey <[email protected]>
599ae08
to
8f6490e
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.
/approve
Thank you @brianmcarey !
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dhiller 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 |
[fe4dac8 Run go run ./robots/cmd/kubevirtci-bumper -ensure-last-three-minor-of v1 --k8s-provider-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-provision/k8s](kubevirt/kubevirtci#1394) [cb8dee6 k8s-1.33: Update url to check previous k8s version](kubevirt/kubevirtci#1396) [60517a0 k8s-1.33: Add new provider for Kubernetes version 1.33](kubevirt/kubevirtci#1392) ```release-note NONE ``` Signed-off-by: kubevirt-bot <[email protected]>
[fe4dac8 Run go run ./robots/cmd/kubevirtci-bumper -ensure-last-three-minor-of v1 --k8s-provider-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-provision/k8s](kubevirt/kubevirtci#1394) [cb8dee6 k8s-1.33: Update url to check previous k8s version](kubevirt/kubevirtci#1396) [60517a0 k8s-1.33: Add new provider for Kubernetes version 1.33](kubevirt/kubevirtci#1392) ```release-note NONE ``` Signed-off-by: kubevirt-bot <[email protected]>
[fe4dac8 Run go run ./robots/cmd/kubevirtci-bumper -ensure-last-three-minor-of v1 --k8s-provider-dir /home/prow/go/src/github.com/kubevirt/project-infra/../kubevirtci/cluster-provision/k8s](kubevirt/kubevirtci#1394) [cb8dee6 k8s-1.33: Update url to check previous k8s version](kubevirt/kubevirtci#1396) [60517a0 k8s-1.33: Add new provider for Kubernetes version 1.33](kubevirt/kubevirtci#1392) ```release-note NONE ``` Signed-off-by: kubevirt-bot <[email protected]>
What this PR does / why we need it:
The old URL used to check the previous kubernetes version no longer exists for versions greater than v1.31 - this is causing the provisioning of the k8s-1.33 provider to fail[1]
Update to get the version from the kubevirtci repo itself.
[1] https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_project-infra/4010/rehearsal-check-provision-k8s-1.33/1899779863519170560#1:build-log.txt%3A166
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
/cc @dhiller
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
Release note: