CMP-4147: override e2e-deployment test to use OCP 4.22 cluster

[rhmdnd]

This is necessary for testing ComplianceAsCode/compliance-operator#1124
which relies on OpenShift API features only available in 4.22.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

Summary by CodeRabbit

Updates the compliance-operator e2e AWS deployment CI workflow to run against an OpenShift 4.22 nightly release image, enabling tests that depend on APIs introduced in OCP 4.22 while preserving the existing 4.17 configuration.

[openshift-ci-robot]

@rhmdnd: This pull request references CMP-4147 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

This is necessary for testing ComplianceAsCode/compliance-operator#1124
which relies on OpenShift API features only available in 4.22.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhmdnd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/ComplianceAsCode/compliance-operator/OWNERS [rhmdnd]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: c5fe3c3c-1872-4396-9221-a78118992536

📥 Commits

Reviewing files that changed from the base of the PR and between 651caa0 and 58455b4.

📒 Files selected for processing (1)

• ci-operator/config/ComplianceAsCode/compliance-operator/ComplianceAsCode-compliance-operator-master.yaml

---

Walkthrough

The compliance-operator CI configuration adds an ARM64 OCP 4.22 nightly release candidate and updates the AWS end-to-end deployment test to use its release image.

Changes

Compliance Operator Release Configuration

Layer / File(s)	Summary
4.22 release candidate and deployment wiring ci-operator/config/ComplianceAsCode/compliance-operator/ComplianceAsCode-compliance-operator-master.yaml	Adds latest-4-22 under releases.arm64-latest and sets OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE for e2e-aws-deployment to release:latest-4-22.

Estimated code review effort: 2 (Simple) | ~5 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: overriding the e2e deployment test to use an OCP 4.22 cluster.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The PR only changes a CI operator YAML file; no Ginkgo It/Describe/Context/When titles were added or modified.
Test Structure And Quality	✅ Passed	Only a CI operator YAML changed; no Ginkgo test code, assertions, or waits were modified, so this test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only changes ci-operator YAML; no Go/Ginkgo test code was added, and the diff contains no new test declarations or MicroShift-sensitive API references.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only ci-operator YAML changed; no new Ginkgo/e2e tests or topology-sensitive code was added, so the SNO check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Only CI operator test config changed; no manifests/controllers or scheduling constraints were added.
Ote Binary Stdout Contract	✅ Passed	Only a ci-operator YAML was changed; no process-level code or stdout writes in OTE binaries were introduced.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only changes CI operator YAML release/dependency config; no new Ginkgo tests or network/IP-logic code were added, so the check is not applicable.
No-Weak-Crypto	✅ Passed	Only CI YAML changed; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons found in the modified file.
Container-Privileges	✅ Passed	The diff only adds a release override; no privileged, hostPID/Network/IPC, SYS_ADMIN, or allowPrivilegeEscalation fields were added.
No-Sensitive-Data-In-Logs	✅ Passed	Only a CI config release override was added; no log statements or secret/token/password/PII fields appear in the change.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[rhmdnd]

cc: @vickeybrown for reviews since we're working through the TLS adherence changes for CO and FIO.

[openshift-ci]

@rhmdnd: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ci-operator-config-metadata	58455b4	link	true	/test ci-operator-config-metadata

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@rhmdnd: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-deployment	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-parallel	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-parallel-arm	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-scan-config	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-serial	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-e2e-aws-serial-arm	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-e2e-rosa	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-go-build	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-images	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-unit	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-master-verify	ComplianceAsCode/compliance-operator	presubmit	Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.