Epic Goal

• ConfigurationPolicies can be used to create/manage resources related to OLM operators, but there are some complexities that are difficult for users.
• We should make it easier to use RHACM policies to install, monitor, and manage OLM operator installations.

Why is this important?

• Installing/Uninstalling Operators is a frequent task. We are promoting installing Operators with OLM.
• Creating an OLM Subscription might be enough to install an operator, but deleting the Subscription (for example with ConfigurationPolicy's pruneObjectBehavior) is not enough to uninstall the operator.
• Additional ConfigurationPolicies would need to be created to monitor the health of an operator, for example a user might need to define a ConfigurationPolicy for each deployment that the operator defines, in order to monitor whether those are healthy.

Scenarios

1. Remove the operator from the managed cluster, by removing the policy.

Acceptance Criteria

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

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>