-
Notifications
You must be signed in to change notification settings - Fork 262
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
🌱 Bump k8s, CR, CG and deps #2395
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/test pull-cluster-api-provider-openstack-e2e-full-test |
/hold |
/test pull-cluster-api-provider-openstack-e2e-full-test |
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one nit below. This looks otherwise good to me
What's the thinking behind the bump to unreleased CAPI? |
To get the new API changes and test everything is alright before they release as well. CAPV does it as well. |
/test pull-cluster-api-provider-openstack-e2e-full-test |
/test pull-cluster-api-provider-openstack-e2e-full-test |
can we please land this one? unless there is pushback. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine with this and I think it is good to test the latest CAPI code. We should point to a proper release when we push tags though.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EmilienM 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 |
/test pull-cluster-api-provider-openstack-e2e-full-test |
/hold |
/hold cancel |
What this PR does / why we need it:
go.mod updates
API violations
Update CAPI API violations
Generated code
Run
make generate
to produce new code.Bump CAPI to future 1.10 in e2e
In the e2e configuration, we now deploy CAPI from a nightly build to get the future 1.10 version (unreleased now).