Undefined From jkulikau@redhat.com:
We have had, and will likely continue to have, inconsistency in OperatorPolicy tests because we do not control the operators that we test the deployments of. Is there a sample operator, with known working/nonworking versions, and a stable upgrade graph that we could use for our tests? Or should we consider building one for ourselves?
Acceptance Criteria:
- Having an operator packaged by OLM in its own catalog used to replace all operator policy E2E tests in the config-policy-controller repo.
- All the code should live in the config-policy-controller repo and images should be built for the test on demand as opposed living in quay.io.
Helpful links:
https://sdk.operatorframework.io/docs/olm-integration/tutorial-bundle/
https://sdk.operatorframework.io/docs/building-operators/golang/tutorial/
