Value Statement

It's possible to install an operator on a managed cluster (for example through the Openshift UI), and then define the OperatorPolicy for it. The OperatorPolicy should be able to find the created Subscription and OperatorGroup, and recognize if those match the definitions in the OperatorPolicy.

Definition of Done for Engineering Story Owner (Checklist)

• I can install an Operator, and then define an OperatorPolicy, and the policy should be compliant or non-compliant depending on whether the operator matches the policy.
• Syntax errors are reported in case of API version skew in the future (typed -> dynamic -> create/update with strict field validation).

Development Complete

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

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

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.