Epic Goal

Fix some issues that exist with the simplicity of addon templates, make it easy to manage other Red Hat Operators in a way that makes them seem like a cohesive part of the product.

Why is this important?

1. Ease of use for our customers

2. Enablement for OPP

3. Improves likely hood of cross product collaboration

Scenarios

1. As an administrator, I need to be able to deploy CNV and MTV to the hub cluster is a repeatable way
2. As an adminstrator, I need to be able to uninstall CNV and MTV under certain circumstances:
   1. Tearing down the environment, remove everything
   2. Removing ACM management but leaving the environment
   3. Having the default behavior not to remove resources for mission critical components.
3. Do 1 and 2 on ManagedClusters as well.

Acceptance Criteria

1. Install and operator using an addon with additional resources
2. Have that operator remain functioning when there is a problem with the agent and it accidentally issues an uninstall
3. Uninstall the addon connect, but none of the operator components
4. Uninstall the addon and clean up all the operator components

Dependencies (internal and external)

1. OperatorPolicy

Previous Work (Optional):

1. CNV and MTV Addon templates

Done Checklist

• DEV OperatorPolicy - Supports cleanup via an annotation (current required changing to MustNotHave
• DEV ConfigTempltae -
  • OPTIONAL: Each resource defined in the template should allow for a setting of whether to prune or NOT.
  • REQUIRED - Being able to enable/disable pruning for the entire template manifest
• DEV AddonConfig -  When removing an addon, there should be an override for  pruning resources. This would only prune resources that were NOT tagged in the ConfigTemplate to be left behind.
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)