Skip to content

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

Open
30 of 73 tasks
Tracked by #10852
fabriziopandini opened this issue Mar 10, 2025 · 3 comments
Open
30 of 73 tasks
Tracked by #10852

Tracking issue for v1Beta2 #11947

fabriziopandini opened this issue Mar 10, 2025 · 3 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@fabriziopandini
Copy link
Member

fabriziopandini commented Mar 10, 2025

Introduce the new API type

P0: mandatory for first alpha
P1: nice 2 have for first alpha

Introduce support for compatible contracts

Improving status Implementation Phase2 (1.11)

Others

  • [P1] Think about version of the Cluster object embedded in lifecycle hooks
  • Consider if to run a new scale test (e.g. we changed which changes are relevant for the topology reconciler)
  • [P0] Consider dropping 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

  • Drop fake objects from controller tests and use the test/util/builders package
@k8s-ci-robot k8s-ci-robot added needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 10, 2025
@fabriziopandini fabriziopandini added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Mar 10, 2025
@k8s-ci-robot k8s-ci-robot removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. labels Mar 10, 2025
@fabriziopandini fabriziopandini self-assigned this Mar 10, 2025
@sbueringer sbueringer added this to the v1.11 milestone Mar 10, 2025
@fabriziopandini fabriziopandini changed the title Tracking issue for Improving status in CAPI resources - Phase 2 Tracking issue for v1Beta2 Mar 12, 2025
@sivchari
Copy link
Member

sivchari commented May 6, 2025

Hi, @fabriziopandini
If it's ok, can I work on Create v1beta2 types for CAPD(ev) (ensure v1beta1 uses v1beta1 conditions, ...) ?
However, I don't fully understand the steps to take, so it may take some time to respond. If it seems urgent, I can't proceed. If I can proceed, would it be better to refer to the implementation at #12037?

@fabriziopandini
Copy link
Member Author

@sivchari your offer is really appreciated.
I will try to add more details / pointers to previous PRs for Create v1beta2 types for CAPD(ev) (ensure v1beta1 uses v1beta1 conditions, ...) ASAP

@fabriziopandini
Copy link
Member Author

fabriziopandini commented May 6, 2025

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants