Value Statement

It's possible to create a ConfigurationPolicy for an OLM Subscription that should install an operator, but without additional policies it is hard to verify whether its installation was successful or not. The new OperatorPolicy type should make it easy to do with just one policy.

Definition of Done for Engineering Story Owner (Checklist)

A policy like this should be able to be applied to a cluster, and will only become compliant when the operator is successfully installed and running:

apiVersion: policy.open-cluster-management.io/v1beta1
kind: OperatorPolicy
metadata:
  name: strimzi-policy
spec:
  remediationAction: enforce
  severity: medium
  complianceType: musthave
  subscription:
    channel: stable
    name: strimzi-kafka-operator
    namespace: openshift-operators
    installPlanApproval: Manual
    source: community-operators
    sourceNamespace: openshift-marketplace
    startingCSV: strimzi-cluster-operator.v0.35.0
  versions:
    - strimzi-cluster-operator.v0.35.0 

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.