-
Notifications
You must be signed in to change notification settings - Fork 693
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 v1alpha1 in v0.31.0 #1375
Closed
4 tasks done
Comments
fyi- Warning should land in v0.30 and should be noted in the release notes: #1337 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Jul 9, 2024
/remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Jul 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
v1alpha1 version of the descheduling policy has been deprecated for many releases now. It's time to remove it from the code base and focus on v1alpha3.
Removal announced on sig-scheduling dev list: https://groups.google.com/g/kubernetes-sig-scheduling/c/OyFjkDntuhg/m/GVjD4gpaBAAJ?utm_medium=email&utm_source=footer
1.30 k8s release scheduled for Wednesday 17th April 2024: https://www.kubernetes.dev/resources/release/#summary
TODO:
The text was updated successfully, but these errors were encountered: