Skip to content
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
ingvagabund opened this issue Apr 9, 2024 · 3 comments · Fixed by #1482 or #1498
Closed
4 tasks done

Remove v1alpha1 in v0.31.0 #1375

ingvagabund opened this issue Apr 9, 2024 · 3 comments · Fixed by #1482 or #1498
Assignees

Comments

@ingvagabund
Copy link
Contributor

ingvagabund commented Apr 9, 2024

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:

  • - remove v1alpha1 types from the code
  • - remove v1alpha1 -> v1alpha2 conversion code
  • - remove any mention of v1alpha1 type from the documentation (probably just mentioning v1alpha1 was removed in 0.31.0)
  • - announce v1alpha1 removal on sig-scheduling dev list + descheduler changelogs
@a7i
Copy link
Contributor

a7i commented Apr 10, 2024

fyi- Warning should land in v0.30 and should be noted in the release notes: #1337

@damemi damemi pinned this issue Apr 23, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot 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
@a7i
Copy link
Contributor

a7i commented Jul 9, 2024

/remove-lifecycle stale

@k8s-ci-robot 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
@ingvagabund ingvagabund reopened this Aug 15, 2024
@ingvagabund ingvagabund self-assigned this Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants