Background

When CAPI Machines have infrastructureReady false or omitted, or have non-zero deletion timestamp we should prevent changing the .spec.authoritativeAPI (i.e. trigger a migration) to avoid unpredictable issues given the transitioning state of the machine/instance. 

Behaviours

• Reject updates to a CAPI Machine's MAPI mirror .spec.authoritativeAPI if CAPI Machine's .status.infrastructureReady
  is false or omitted
• Reject updates to a CAPI Machine's MAPI mirror .spec.authoritativeAPI if .metadata.deletionTimestamp is non-zero

Steps

• Explore using VAP for Machine validation in CAPI
•  

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>