Epic Goal

• Currently, our Gauge-based test suite (release-tests) is executed manually or asynchronously. To improve reliability and catch regressions proactively, we need to onboard these tests into OpenShift CI as scheduled weekly jobs (Periodics).

This Epic covers the end-to-end setup: from preparing the cluster profiles and Vault secrets, to configuring the Prow job definitions, and finally setting up alerting for test failures.

Scope:

• Configure necessary cluster profiles (e.g., AWS/GCP) and Boskos quota-slices.

• Sync necessary SSH keys and cloud credentials via the OpenShift Vault UI.

• Create the periodic job definitions in the openshift/release repository.

• Ensure the test container image correctly utilizes Go 1.24.4 and initializes the Gauge Go runner.

• Route failure notifications to the team's designated Slack channel.

Why is this important?

• To minimize the release-testing efforts for patch and minor releases for all OCP versions
• This helps us to run the release operator on all supported OCP versions weekly
• Helps the team focus on feature testing and other qe focus areas

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment