Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-11160

Create or reuse a fake operator for OperatorPolicy testing

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • GRC
    • GRC Sprint 2024-09, GRC Sprint 2024-10, GRC Sprint 2024-11, GRC Sprint 2024-12, GRC Sprint 2024-13, GRC Sprint 2024-14, GRC Sprint 2025-01, GRC Sprint 2025-02
    • No

      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/

              yikim@redhat.com Yi Rae Kim
              mprahl Matthew Prahl
              Derek Ho Derek Ho
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: