Epic Goal

• Allow administrators to define which machineconfigs won't cause a drain and/or reboot.
• Allow administrators to define which ImageContentSourcePolicy/ImageTagMirrorSet/ImageDigestMirrorSet won't cause a drain and/or reboot
• Allow administrators to define what services need to be started or restarted after writing the new config file.

Why is this important?

• There is a demonstrated need from customer cluster administrators to push configuration settings and restart system services without restarting each node in the cluster. 
• Customers are modifying ICSP/ITMS/IDMS outside post day 1/adding them+

Scenarios

1. As a cluster admin, I want to reconfigure sudo without disrupting workloads.
2. As a cluster admin, I want to update or reconfigure sshd and reload the service without disrupting workloads.
3. As a cluster admin, I want to remove mirroring rules from an ICSP, ITMS, IDMS object without disrupting workloads because the scenario in which this might lead to non-pullable images at a undefined later point in time doesn't apply to me.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>