Background

To ensure higher level objects continue to operate as expected (cluster-autoscaler,mhc) we define a synchronisation of deletions for MAPI and CAPI mirrors.

The behaviours outlined below will ensure that the resources continue to operate as expected and should be implemented in both the Machine and MachineSet controllers.

Behaviours

• Ensure sync.machine.openshift.io/finalizer is present on both copies of mirrored resources
• Propagate deletionTimestamp from authoritative resource to non-authoritative
• Propagate deletionTimestamp if non-authoritative and has an owner reference (eg Machine owned by MachineSet)
• Remove sync finalizer from both resources when authoritative deletion finalizer is removed (start with non-authoritative)

Steps

• Implement finalizer addition and removal in Machine and MachineSet synchronization controllers based on behaviours outlined above

Stakeholders

• Cluster Infra

Definition of Done

• Deletion of MAPI/CAPI resources is synchronised as defined above

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>