-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Tracking issue for v1Beta2 #11947
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
Comments
Hi, @fabriziopandini |
@sivchari your offer is really appreciated. |
@sivchari I broke down "Create v1beta2 types for CAPD(ev) (ensure v1beta1 uses v1beta1 conditions, ...)" into 4 sequential steps, linking to priort art PRs for the core APIs. If you need more clarification for some step, feel free to ping me in slack |
Introduce the new API type
P0: mandatory for first alpha
P1: nice 2 have for first alpha
Introduce support for compatible contracts
⚠️ Implement v1beta2 contract in cluster controller, KCP, CABPK #12094
Improving status Implementation Phase2 (1.11)
Initialized
condition instead of theAvailable
condition to calculate remoteConditionsGracePeriodOthers
DefaulterRemoveUnknownOrOmitableFields
option on CAPI mutating web hooks (clarify pro & cons with @sbueringer first)Backlog for improving status
Looking for volunteers (like everything else MachinePools)
If and when we have bandwidth
The text was updated successfully, but these errors were encountered: