-
Notifications
You must be signed in to change notification settings - Fork 249
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
Remove kubernetes 1.27 from supported versions #3247
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
/assign |
bf855bc
to
7f999cf
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vladikkuzn The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
7f999cf
to
ae8dfdf
Compare
ae8dfdf
to
ff9a34f
Compare
if v.String() == "" || v.LessThan(kubeversion.KubeVersion1_27) { | ||
return false, fmt.Errorf("kubernetesVersion %q: %w", v.String(), errPodNoSupportKubeVersion) | ||
} | ||
func CanSupportIntegration(_ ...jobframework.Option) (bool, error) { |
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.
Can we remove this function as well? It seems to be optional.
As we discussed here we should merge this after Kueue 0.9 release is finalized. /hold |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Removes skip of tests which are not supported on k8s with version less then 1.27, since we are running tests on 1.28+
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Done per discussion here: #3001 (comment)
Does this PR introduce a user-facing change?