Epic Goal

Automate the Gatekeeper operator tests so they can be automatically executed during the release process with a reasonably good support matrix coverage.

Why is this important?

QE tests the Gatekeeper operator during the ACM testing cycle. Gatekeeper is getting decoupled from ACM from a release standpoint, so we need a way to automatically provision an environment to test Gatekeeper on the minimum and maximum supported OpenShift versions as well as test the ACM integration with Gatekeeper.

This testing should be automatically executed in the "QE" phase of an environment and Container Verification Pipeline (CVP) should be configured to gate on these test results being reported.

This will allow QE's effort to be focused on advising engineering on test cases rather than setting up the environment and executing tests.

Scenarios

See each task for more details.

Acceptance Criteria

See each task for more details.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. The OPP QE Interop work may inspire us for the environment provisioning:
   https://github.com/openshift/release/blob/master/ci-operator/config/stolostron/policy-collection/stolostron-policy-collection-main__opp-ocp4.12-interop.yaml

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>