Tracking issue for Improving status in CAPI resources - Phase 1

[fabriziopandini]

This is a tracking issue for activities related to #10897

Enablement

Activities that are required to unblock implementation

• @fabriziopandini Implement conditions utils ✨ Implement utils for v1beta2 conditions #10997
• @fabriziopandini Add support for metav1 conditions in patch helper 🌱 Add support for v1beta2 conditions to patch helper #11150
• @sbueringer Improve Cluster Cache Tracker to allow tracking of connection problems ✨ Introduce new ClusterCache #11247
• @chrischdi MD foreground deletion 🌱 Foreground deletion for MachineDeployments and MachineSets #11174
• @sbueringer Handle finalizers early in Reconciles#11286

Documentation updates

• @fabriziopandini add superseded by notice to old condition proposal ⚠️ Add superseded notice to the old condition proposal #11189)
• @fabriziopandini update provider contracts with notices about future changes & clarify requirements about conditions in provider contracts. Note, no backport is planned
  • @fabriziopandini 📖 Drop k8s.gcr.io deprecation notice #11190
  • @fabriziopandini 📖 Drop old version of migration docs #11191
  • @fabriziopandini 📖 Group API reference docs #11194
  • @fabriziopandini 📖 Refactor provider's implementers guide #11195
  • @fabriziopandini 📖 Refactor core developer guide #11208
  • @fabriziopandini 📖 Refactor InfraCluster contract #11213
  • @fabriziopandini 📖 Refactor InfraMachine contract #11223
  • @fabriziopandini 📖 Refactor the BootstrapConfig contract #11235
  • @fabriziopandini 📖 Refactor ControlPlane contract #11285
  • machine pool contract

Implementation Phase1

Focus on phase 1 of the implementation, where new field are added but not yet used by controllers

• API modeling
  • @fabriziopandini ✨ Add v1beta2 structs to object status #11234
  • @chrischdi 🌱 api: deprecate FailureMessage and FailureReason #11317
• Machine controller
  • @fabriziopandini ✨ Update machine with v1beta2 status #11276
  • @fabriziopandini KCP ✨ Add machine UpToDate condition to KCP #11389
  • @fabriziopandini ✨ Add machine UpToDate condition to MachineSet #11393
  • @sbueringer 🌱 Implement Machine Deleting condition #11291
• MachineHealthCheck controller
  • @fabriziopandini ✨ Update MHC with v1Beta2 status #11290
• MachineSet controller
  • @chrischdi ✨ Update machineset with v1beta2 status test #11278
  • @sbueringer 🌱 Implement MS remediating conditions  #11382
  • @sbueringer 🌱 Implement MS remediating conditions  #11382
  • @sbueringer 🌱 Implement KCP and MS Deleting conditions #11381
  • @sbueringer 🌱 Extend MS ScalingUp and Remediationg conditions to include preflight check errors #11390
• MachineDeployment controller
  • @fabriziopandini ✨ Add v1beta2 condition to MD controller #11338
• KubeadmControlPlane controller
  • @fabriziopandini ✨ Add v1beta2 Etcd and ControlPlaneComponents conditions to KCP #11302
  • @fabriziopandini ✨ Add v1beta2 available condition to KCP #11383
  • @sbueringer 🌱 Implement KCP and MS Deleting conditions #11381
  • @chrischdi 🌱 kcp: ensure ReadinessGates for v1beta2 conditions get set #11335
  • @fabriziopandini ✨ Add v1beta2 OwnerRemediated condition to KCP #11297
  • @fabriziopandini ✨ Add v1beta2 Etcd and ControlPlaneComponents conditions to KCP #11302
  • @sbueringer 🌱 Implement grace period for KCP remote conditions #11339
• Cluster controller
  • @fabriziopandini ✨ Add v1beta2 condition to Cluster controller #11364
  • @sbueringer ✨ Introduce new ClusterCache #11247
• Topology controller
  • @sbueringer 🌱 Implement Cluster TopologyReconciled v1beta2 condition #11394
• ClusterClass controller
  • @sbueringer 🌱 Add v1beta2 conditions to ClusterClass #11428
• KubeadmConfig controller
  • @fabriziopandini 🌱 Add v1beta2 conditions to CABPK #11452
• ClusterResourceSet, ClusterResourceSetBinding
  • @chrischdi 🌱 crs: implement ResourcesApplied v1beta2 condition #11467
• clusterctl describe cluster
  • @fabriziopandini ✨ Add support for v1beta2 conditions to clusterctl describe #11277

Follow up / before release

Activities that could be deferred to after we get a first version of this proposal implemented

• P0: Check initializations of the status structs to catch cases like this
• P0: Double check deprecations notices: fields that are marked as deprecated in the proposal, utils, etc ⚠️ Deprecate replica counters planned for removal #11516 (note: we used deprecation to give an early notice to users only in case of fields that are going to be removed, not for field that will continue to exist with a different semantic)
• P0: Prune fields not yet implemented before release

Phase 2 activities are tracked in #11474