AUTOSCALE-643: Release chores 5.0 for Cluster Resource Override (CRO)

[alaxkar]

Summary

Updates previous-bundle and previous-operator base image references from 4.21 to 4.22 for the cluster-resource-override-admission-operator release-5.0 configuration.

Changes

• Updated previous-bundle base image from 4.21 to 4.22
• Updated previous-operator base image from 4.21 to 4.22

Summary by CodeRabbit

This PR updates the CI operator configuration for the cluster-resource-override-admission-operator's release-5.0 branch in the OpenShift CI infrastructure.

What changed:
The base container images referenced in the CI build configuration have been updated to point to version 4.22 base images instead of 4.21. Specifically, both the previous-bundle and previous-operator image references are now sourced from the newer OCP release version.

Practical impact:
This ensures that CI builds and image generation for the release-5.0 branch of the cluster-resource-override-admission-operator will use the more recent 4.22 base images, keeping the operator's dependencies current with the newer OpenShift release.

[openshift-ci-robot]

@alaxkar: This pull request references AUTOSCALE-643 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 task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Updates previous-bundle and previous-operator base image references from 4.21 to 4.22 for the cluster-resource-override-admission-operator release-5.0 configuration.

Changes

• Updated previous-bundle base image from 4.21 to 4.22
• Updated previous-operator base image from 4.21 to 4.22

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.

[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: da2398d9-b3a4-40eb-9b8d-91d025d59d99

📥 Commits

Reviewing files that changed from the base of the PR and between 8d7c3bf and aebdfca.

📒 Files selected for processing (1)

• ci-operator/config/openshift/cluster-resource-override-admission-operator/openshift-cluster-resource-override-admission-operator-release-5.0.yaml

---

Walkthrough

In the CI operator config for cluster-resource-override-admission-operator release-5.0, the base_images entries for previous-bundle and previous-operator have their name field changed from "4.21" to "4.22". No other fields or sections are modified.

Changes

Base Image Version Bump

Layer / File(s)	Summary
Bump previous-bundle and previous-operator to 4.22 ci-operator/config/openshift/cluster-resource-override-admission-operator/openshift-cluster-resource-override-admission-operator-release-5.0.yaml	previous-bundle.name and previous-operator.name in base_images updated from "4.21" to "4.22"; namespace and tag are unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 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 clearly references the JIRA ticket (AUTOSCALE-643) and describes the main change: release chores for version 5.0 of the Cluster Resource Override operator, which aligns with the base image version updates from 4.21 to 4.22.
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	PR only modifies CI-operator configuration file (base image version updates), not test code. No Ginkgo tests affected.
Test Structure And Quality	✅ Passed	PR contains only YAML configuration changes to base_images versions (4.21→4.22); no Ginkgo test code is added or modified, making this check not applicable.
Microshift Test Compatibility	✅ Passed	This PR only updates CI operator configuration (base image versions), not adding any Ginkgo e2e tests, so the MicroShift Test Compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo e2e tests are added in this PR. The changes only update CI configuration YAML files with base image version references (4.21→4.22), so the SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only CI pipeline configuration metadata (base image version references), not deployment manifests, operator code, or controllers. No scheduling constraints introduced.
Ote Binary Stdout Contract	✅ Passed	Check not applicable. PR updates CI configuration (YAML) files only, not OTE binary code. OTE Stdout Contract check applies to binaries communicating JSON to openshift-tests, not config updates.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR updates CI operator configuration files, not adding any Ginkgo e2e tests. The check requires new tests to be flagged for IPv6/disconnected compatibility issues.
No-Weak-Crypto	✅ Passed	PR only modifies CI/CD configuration YAML with version number updates; no cryptographic code, weak algorithms, or secret comparisons are involved.
Container-Privileges	✅ Passed	PR modifies only base image version references (4.21→4.22) in a CI/CD config file; no container security settings like privileged/hostPID/hostNetwork/SYS_ADMIN/allowPrivilegeEscalation are present...
No-Sensitive-Data-In-Logs	✅ Passed	PR only updates base image version references from 4.21 to 4.22 in a YAML config file. No logging statements, sensitive data, passwords, tokens, API keys, PII, or customer data are present or being...

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: alaxkar
Once this PR has been reviewed and has the lgtm label, please assign jkyros for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/cluster-resource-override-admission-operator/OWNERS

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@alaxkar: 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-openshift-cluster-resource-override-admission-operator-release-5.0-ci-bundle-cluster-resource-override-admission-operator-bundle	openshift/cluster-resource-override-admission-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-resource-override-admission-operator-release-5.0-e2e-aws-olm	openshift/cluster-resource-override-admission-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-resource-override-admission-operator-release-5.0-e2e-aws-operator	openshift/cluster-resource-override-admission-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-resource-override-admission-operator-release-5.0-e2e-aws-upgrade	openshift/cluster-resource-override-admission-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-resource-override-admission-operator-release-5.0-images	openshift/cluster-resource-override-admission-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-resource-override-admission-operator-release-5.0-security	openshift/cluster-resource-override-admission-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-resource-override-admission-operator-release-5.0-unit	openshift/cluster-resource-override-admission-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-resource-override-admission-operator-release-5.0-verify	openshift/cluster-resource-override-admission-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-resource-override-admission-operator-release-5.0-verify-deps	openshift/cluster-resource-override-admission-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.

[openshift-ci]

@alaxkar: all tests passed!

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.