Feature Overview and Background

Changing any configuration (units, files, mirros, kube config etc) via the MCO will trigger a reboot for every node in the pool and some of those changes don't need a reboot.

Problem

Rebooting nodes on on-premise platforms during an MCO configuration rollout requires a significant amount of time (15m+, mainly in POST). A configuration done through the MCO is rotating GPG keys.

Goals / Acceptance Criteria 

• Avoid rebooting and drain in the cases of adding an GPG
• Assess "backport-ability" to 4.7?