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.28 #8708

Closed
13 tasks done
ykakarap opened this issue May 20, 2023 · 22 comments
Closed
13 tasks done

Tasks to bump to Kubernetes v1.28 #8708

ykakarap opened this issue May 20, 2023 · 22 comments
Assignees
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ykakarap
Copy link
Contributor

ykakarap commented May 20, 2023

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

Tasks

Prerequisites:

  • Decide which Cluster API release series will support the new Kubernetes version
    • If feasible we usually cherry-pick the changes back to the latest release series.
    • => As usuall will implement on main and cherry-pick into release-1.5

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.

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 May 20, 2023
@killianmuldoon
Copy link
Contributor

/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 May 21, 2023
@fabriziopandini
Copy link
Member

Thanks for starting planning work for the intake of the upcoming K8s release!
(note, planned release date as of today is Aug 15th)

@sbueringer
Copy link
Member

We mostly opened this issue already so we can start collecting release-specific tasks "somewhere". If someone has other release-specific tasks, please let us know :)

@sbueringer
Copy link
Member

/assign

I've already started working on supporting v1.28 in CR

@chrischdi
Copy link
Member

/assign

After talking to @sbueringer : I'll takeover the Supporting managing and running on the new Kubernetes version part for now.

@furkatgofurov7
Copy link
Member

furkatgofurov7 commented Aug 9, 2023

@sbueringer @chrischdi do you need help with this issue since it is in parts(tracking one)? If so, please let me know and we can distribute it as we did in the prev release cycle :)

@sbueringer
Copy link
Member

sbueringer commented Aug 9, 2023

Thx, I think we're good for now. IIRC Christian should have most of it already locally. For the second section I have to wait for the CR release

(And we can't merge the PRs for the first section before the Kubernetes 1.28 release next week)

@sbueringer
Copy link
Member

sbueringer commented Aug 9, 2023

Would be really good if we can finish #9097 so PRs building on top are not getting too messy (merge conflicts etc)

@chrischdi
Copy link
Member

chrischdi commented Aug 10, 2023

I pre-created PRs for the Supporting managing and running on the new Kubernetes version part.

They should get merged in order and the first one depends on #9097 .

Also the first one depends on the v1.28 release getting done and on getting a kind release.

They are all marked as WIP and draft for now.

Supporting managing and running on the new Kubernetes version

@sbueringer
Copy link
Member

All 3 PRs are merging now. @chrischdi PTAL at cherry-picking the two non-test-infra PRs into release-1.5. I suspect they might need manual cherry-picks

@sbueringer
Copy link
Member

sbueringer commented Aug 17, 2023

So first half is basically done (+/- keeping an eye on testgrid for a bit). The second depends on the CR release

@furkatgofurov7
Copy link
Member

@sbueringer is there a release timeline for CR release?

@sbueringer
Copy link
Member

sbueringer commented Aug 17, 2023

No, probably a few days. But we should have > 2 months time for it in CAPI

@sbueringer
Copy link
Member

sbueringer commented Aug 22, 2023

CR v0.16 was released today. Opened a few PRs for the second section:

I think otherwise we should be done. Would be great if someone can double-check if I/we missed something (@killianmuldoon @chrischdi)

@furkatgofurov7
Copy link
Member

I think otherwise we should be done. Would be great if someone can double-check if I/we missed something

Double checked it and looks like everything is covered with above PRs 👍🏼

@sbueringer
Copy link
Member

@furkatgofurov7 thank you!

@sbueringer
Copy link
Member

sbueringer commented Aug 23, 2023

@kinarashah
Copy link

kinarashah commented Aug 24, 2023

@sbueringer do you know timeline for when this bump to k8s 1.28 would be released?

@sbueringer
Copy link
Member

Next Tuesday

@furkatgofurov7
Copy link
Member

@sbueringer looks like we can close this issue?

@sbueringer
Copy link
Member

Yup

/close

@k8s-ci-robot
Copy link
Contributor

@sbueringer: Closing this issue.

In response to this:

Yup

/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

8 participants