Umbrella issue: API changes

[sbueringer]

Goal of this issue is to provide an overview over issues related to API changes.

ClusterClass & Cluster.spec.topology:

• [ ] #10666 [deprecated] [will be removed in v1beta2]
• [ ] #8211 [not planned]
• [ ] #8210 [not planned]
• [ ] #7521 [deprecated] [will be removed in v1beta2]
• [ ] #6706 [not planned]
• [ ] Consider making .spec.controlPlane mandatory

Cluster:

• [ ] #6416 [waiting for v1beta2]
• [ ] #7538 [waiting for v1beta2]

MachineDeployment:

• [ ] #10479 [deprecated] [will be removed in v1beta2]
• [ ] #6966
• [ ] #10946 (potentially we want to redesign our rollout* fields)

MachineSet

• [ ] Remove --use-deprecated-infra-machine-naming [deprecated] [will be removed in v1.9]

Machine:

• [ ] #9692 [not planned]
• [ ] #7021
• [ ] Check how bootstrap.ref/datasecret are modelled: https://github.com/kubernetes-sigs/cluster-api/issues/10943#issuecomment-2312430651 & check in all the places where we use MachineSpec (MD/MS/MP/...)

KubeadmControlPlane:

• [ ] Remove --use-deprecated-infra-machine-naming [deprecated] [will be removed in v1.9]

KubeadmConfig / KubeadmConfigTemplate / KubeadmControlPlane / KubeadmControlPlaneTemplate:

• [ ] #6942 [deprecated] [will be removed in v1beta2]
• [ ] #4910 [not planned]

MachinePool:

• [ ] #7248 [not planned] [TBD if blocker for MP graduation]

MachineHealthCheck:

• [ ] #10722 [deprecated] [will be removed in v1beta2]
• [ ] #5291 [not planned]
• [ ] Rename conditions to nodeConditions?

ClusterResourceSet:

• [ ] #8267 [waiting for v1beta2]

clusterctl:

• [ ] #10138 [deprecated] [will be removed in v1.9]

Finalizers:

• [ ] #10914

Status fields & conditions:

• [ ] @fabriziopandini (#10897)
  • [x] #7635
  • [x] #10532
  • [x] #10707
  • [x] #7099
  • [x] #3974
  • [x] #3486
  • [x] #5635
  • [ ] #10130
  • [x] #7461
  • [ ] out of scope for the first iteration of the proposal, but the same principles will apply
  • [ ] #8137
• [ ] #10059
• [ ] #6807
• [ ] #5453
• [x] #10056
• [ ] Feedback: #10360

CRD Columns: (can be already done today)

• [ ] @fabriziopandini (#10897)
  • [x] #6238
  • [x] #6227
  • [x] #5332
  • [ ] out of scope for the first iteration of the proposal, but the same principles will apply
  • [ ] #9007

Smaller improvements: (can be already done today)

• [ ] #6504
• [ ] #6397

Bigger changes:

• [ ] #6539

Backlog: (require some design/proposal)

• [ ] #5294
• [ ] #5517

Explanations:

• [waiting for v1beta2]: There is absolutely nothing we can do today, we are just waiting for v1beta2

[sbueringer]

/triage accepted

[sbueringer]

I have 3 PRs open for deprecations for v1.8:

• Deprecate definitionFrom https://github.com/kubernetes-sigs/cluster-api/pull/10841
• Deprecate MHC: https://github.com/kubernetes-sigs/cluster-api/pull/10853
• Deprecate MD revision management: https://github.com/kubernetes-sigs/cluster-api/pull/10855

[sbueringer]

Added all condition issues I could find to the list above. I think there is a huge overlap with #10897 (i.e. most of these issues would be solved if the proposal is implemented). We should check if there are gaps/conflicts

[enxebre]

I think these two can be added to conditions https://github.com/kubernetes-sigs/cluster-api/issues/10056 https://github.com/kubernetes-sigs/cluster-api/issues/5635

[sbueringer]

Thx! added

[enxebre]

this doesn't have an issue associated but I think is valid feedback as well for conditions https://github.com/kubernetes-sigs/cluster-api/pull/10360

[sivchari]

@chrischdi @sbueringer @fabriziopandini Hi folks, I have generous times to do these issues and other issues. I want to contribute more to Cluster API. May I work on these ? Or may I help you with anything ?

[vincepri]

Let's consider having a next branch created specifically for v1beta2 type changes