Background

To be able to continue to operate MachineSets, we need a backwards conversion once the migration has occurred. We do not expect users to remove the MAPI MachineSets immediately, and the logic will be required for when we remove the MAPI controllers.

This covers the case where the CAPI MachineSet is authoritative or only a CAPI MachineSet exists.

Behaviours

• If the MachineSet only exists in CAPI, do nothing
• If the MachineSet is mirrored in MAPI
  • Convert the InfraTemplate to a providerSpec, and update the MAPI resource
  • Mirror labels from the CAPI MachineSet to the MAPI MachineSet
  • Ensure spec and status fields (replicas, taints etc) are mirrored between the MachineSets
• On Failure
  • Set the Synchronized condition to False and apply an appropriate message
• On Success
  • Set the Synchronized condition to True and update the synchronizedGeneration

Steps

Stakeholders

• <Who is interested in this/where did they request this>

Definition of Done

• <Add items that need to be completed for this card>

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>