-
Notifications
You must be signed in to change notification settings - Fork 218
Upgrade to CAPI v1.11 #1509
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
base: main
Are you sure you want to change the base?
Upgrade to CAPI v1.11 #1509
Conversation
justinsb
commented
Aug 23, 2025
- chore: bump CAPI dependencies to 1.11.0
- chore: replace imports for CAPI 1.11
- chore: inline v1beta1 helper utils to enable upgrade
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
✅ Deploy Preview for kubernetes-sigs-cluster-api-gcp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
We discussed this in CAPI office hours this week. It's a big process https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.10-to-v1.11, but we should be able to start gradually by just bumping the dependency and sticking with v1beta1. A "real" integration will start using v1beta2 upstream, and then bump our own types to v1beta2 (the big change is status.conditions, I believe) Have we documented our branching strategy anywhere? I would imagine that the release-1.10 branch maps to CAPI 1.10, and we cherry-pick fixes for 1.10 to that branch. If we don't have a doc, I'm happy to send a PR |
050fd9a
to
ed6b043
Compare
4bb63a7
to
459eab7
Compare
@justinsb: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
Thanks @justinsb. Looks like this bump also requires a number of changes to remove deprecated functions. Let me know if I can help collaborating on this PR. |
there are a few issues
|