Tracking issue for v1Beta2 - MachinePools

[richardcase]

This is to track the v1beta2 changes for machine pools and is an extension of the other v1beta2 work being tracked on #11947

From proposal

• Disambiguate the usage of the ready term by renaming fields used for the initial provisioning workflow - ⚠️ Add initialization to MachinePool Status #12102 - Matt to confirm
• Update ReadyReplicas counter to use the same semantic Machine's Ready condition and add missing UpToDateReplicas - ⚠️ Promote v1beta2 conditions #12066 - Matt to confirm
• Align MachinePools replica counters to other CAPI resources - Rich
  • [v1beta2] MachinePool align replica counters #12413
• Remove FailureReason and FailureMessage to get rid of the confusing concept of terminal failures - Matt to confirm
• Transition to new, improved, K8s API conventions aligned conditions

From parent issue

• MachinePool conditions
  • Implement conditions on MachinePools and MachinePool Machines (UpToDate)
  • Revert 🐛 Disable aggregation of not reported MachinePool conditions for Cluster #11416
• DockerMachinePool
  • Add v1beta2 struct
  • Paused

Other things

• Find a better solution for bootstrap.dataSecretName="" for machine pools (especially "managed" varieties) see 🐛 Relax minLength for bootstrap.dataSecretName to 0 #12164
• Add MachinePool contract documentation as per @fabriziopandini comment(Tracking issue for v1Beta2 - MachinePools #12178 (comment))
• Observed generation is changing , even if there are no changes MachinePool observedGeneration is updated without changing conditions on upgrades #10059
• ClusterClass bootstrap changes probably don't cause a rollout ClusterClass MachinePool implementation is probably not able to rollout BootstrapConfig changes. #10496
• Move conditions setting to the update status

/area machinepool
/area api

[richardcase]

/priority important-soon
/assign
/assign mboersma

[fabriziopandini]

If you all agree I would add to the tracking issue the work for implementing a page for MP contract documentation under https://cluster-api.sigs.k8s.io/developer/providers/contracts/overview

note: we have something under https://cluster-api.sigs.k8s.io/developer/core/controllers/machine-pool but this is the wrong place, and also we should align the documentation to what has been done e.g. for https://cluster-api.sigs.k8s.io/developer/providers/contracts/infra-machine (or other contracts)

The main advantage is that this could help to start consolidating the knowledge about various MP incantations that exists and their implications in core Cluster API thus avoiding discussion/issues like e.g. #12164 (comment)

[chrischdi]

/triage accepted