Goal

As a cluster admin, I want Argo CD to automatically prevent node reboots when syncing OpenShift cluster configuration such as MachineConfigs so that I can use Argo CD for syncing OpenShift configurations without causing uncontrolled and multiple node reboots across the cluster during the sync.

When changes are made to a machine configuration on OpenShift, the Machine Config Operator (MCO) automatically reboots all corresponding nodes in order for the changes to take effect:
https://docs.openshift.com/container-platform/4.7/architecture/control-plane.html#understanding-machine-config-operator_control-plane

The reboot during an Argo CD sync can lead to the Argo CD pod to get rescheduled in the middle of the sync and create undesirable outcomes. Furthermore, a sync can cause mulitple consequent reboots if multiple machine config changes are applied.

As a workaround, customers currently have to manually disable node reboot on MachineConfigs via an oc patch, sync the configs with Argo CD, and reenable reboot to get the changes applied:

• https://docs.openshift.com/container-platform/4.7/support/troubleshooting/troubleshooting-operator-issues.html#troubleshooting-disabling-autoreboot-mco_troubleshooting-operator-issues
• https://access.redhat.com/solutions/5635421

Acceptance Criteria

• Admin can use Argo CD Application for syncing OpenShift cluster configurations in a way that node reboots automatically occur only when sync is complete