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

Tasks to bump to Kubernetes v1.30 #10026

Closed
12 of 13 tasks
sbueringer opened this issue Jan 19, 2024 · 8 comments · Fixed by #10610
Closed
12 of 13 tasks

Tasks to bump to Kubernetes v1.30 #10026

sbueringer opened this issue Jan 19, 2024 · 8 comments · Fixed by #10610
Assignees
Labels
area/dependency Issues or PRs related to dependency changes kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sbueringer
Copy link
Member

sbueringer commented Jan 19, 2024

This issue is tracking the tasks that should be implemented after the Kubernetes minor release has been released.

Tasks

Note: If feasible we usually cherry-pick the changes back to the latest release series.

Supporting managing and running on the new Kubernetes version

This section contains tasks to update our book, e2e testing and CI to use and test the new Kubernetes version
as well as changes to Cluster API that we might have to make to support the new Kubernetes version. All of these
changes should be cherry-picked to all release series that will support the new Kubernetes version.

Bump quickstart and kind image references in CAPD

Prerequisites:

Using new Kubernetes dependencies

This section contains tasks to update Cluster API to use the latest Kubernetes Go dependencies and related topics
like using the right Go version and build images. These changes are only made on the main branch. We don't
need them in older releases as they are not necessary to manage workload clusters of the new Kubernetes version or
run the Cluster API controllers on the new Kubernetes version.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 19, 2024
@sbueringer
Copy link
Member Author

/assign
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 19, 2024
@fabriziopandini
Copy link
Member

/area dependency

@k8s-ci-robot k8s-ci-robot added the area/dependency Issues or PRs related to dependency changes label Jan 19, 2024
@chrischdi
Copy link
Member

@sbueringer
Copy link
Member Author

@chrischdi Let's rewrite the issue description & template once we have consensus on how we want to change the process (e.g. multi-step bump towards a new Kubernetes version)

@chrischdi
Copy link
Member

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 10, 2024
@fabriziopandini
Copy link
Member

/priority important-soon

@sbueringer
Copy link
Member Author

kind was just released so I think we can now complete "Bump quickstart and kind image references in CAPD"

@chrischdi
Copy link
Member

I will take that over :-)

@chrischdi chrischdi linked a pull request May 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependency Issues or PRs related to dependency changes kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants