-
Notifications
You must be signed in to change notification settings - Fork 1.4k
⚠️ Bump Runtime Hooks v1alpha1 types to core CAPI v1beta2 #13200
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 Runtime Hooks v1alpha1 types to core CAPI v1beta2 #13200
Conversation
|
/test pull-cluster-api-e2e-conformance-ci-latest-main |
|
/hold |
Signed-off-by: Stefan Büringer buringerst@vmware.com
448bde4 to
4b48808
Compare
|
Rebased onto latest main /test pull-cluster-api-e2e-conformance-ci-latest-main |
|
@sbueringer: The following test 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. DetailsInstructions 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. |
|
Great to see this change happening, and in a way that minimize impacts on users. |
|
LGTM label has been added. DetailsGit tree hash: 406425639c75a12a7efd32d65211b5a3c76ec123 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold cancel |
Signed-off-by: Stefan Büringer buringerst@vmware.com
What this PR does / why we need it:
This PR bumps the embedded core CAPI API types in the v1alpha1 Runtime Hooks API to v1beta2.
Otherwise these APIs would entirely break once we remove the v1beta1 core CAPI API types.
This should be okay given the API guarantees of v1alpha1 APIs (the impact on users should be also minimal)
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Part of #11920