Open sbueringer opened 1 month ago
/triage accepted
I have 3 PRs open for deprecations for v1.8:
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
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
Thx! added
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
@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 ?
Let's consider having a next
branch created specifically for v1beta2 type changes
Goal of this issue is to provide an overview over issues related to API changes.
ClusterClass & Cluster.spec.topology:
Cluster:
MachineDeployment:
MachineSet
--use-deprecated-infra-machine-naming
[deprecated] [will be removed in v1.9]Machine:
KubeadmControlPlane:
--use-deprecated-infra-machine-naming
[deprecated] [will be removed in v1.9]KubeadmConfig / KubeadmConfigTemplate / KubeadmControlPlane / KubeadmControlPlaneTemplate:
MachinePool:
MachineHealthCheck:
ClusterResourceSet:
clusterctl:
Finalizers:
Status fields & conditions:
CRD Columns: (can be already done today)
Smaller improvements: (can be already done today)
Bigger changes:
Backlog: (require some design/proposal)
Explanations: