Value Statement

To complete this epic, either we create a new opreator management addon that teams can use, or we improve the existing templating and operatorPolicy capabilities.

1. Addon Dependencies is an open Epic for 2.16, this will allow a given addon to require the OperatorPolicy addon.
2. OperatorPolicy kind is great at deploying an operator, but there is no way to have it remove that operator without changing the spec.  With simple addonTemplates, you can only create and delete the operatorPolicy resource. (we need an annotation) that triggers a delete in the same way setting "MustNotHave" does.
3. AddonTemplates need when being written to the manifestWork, need to support an attribute on the resource in the template manifest, that determines if the resource should be pruned or not.
4. A deployed AddonTemplate, when being removed, should also be able to determine, whether it deletes all manifest resources or NOT. Example: I may want to remove ACM management, disconnect a ManagedCluster, but I do NOT want the HCP or CNV addons removed which would interupt my HCP and VM workloads.

Definition of Done for Engineering Story Owner (Checklist)

• We decide to enhance our existing technologies, or build a new one.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.