NO-ISSUE: [master] Bump OCP versions: 5.0, 4.19, 4.21, 4.22, 4.16, 4.20, 4.18

[andrej1991]

OpenShift updates: 4.22.0 -> 4.22.2, 4.22.0-multi -> 4.22.2-multi, 4.20.24 -> 4.20.26, 4.20.24-multi -> 4.20.26-multi, 4.19.33-multi -> 4.19.35-multi, 4.18.43-multi -> 4.18.45-multi, 4.19.33 -> 4.19.35, 4.16.63-multi -> 4.16.64-multi, 4.21.19 -> 4.21.21, 4.18.43 -> 4.18.45, 4.16.63 -> 4.16.64, 4.21.19-multi -> 4.21.21-multi
RHCOS updates: 4.22.0 -> 5.0.0-ec.3

/test edge-e2e-metal-assisted-5-0 edge-e2e-metal-assisted-4-19 edge-e2e-metal-assisted-4-21 edge-e2e-metal-assisted-4-22 edge-e2e-metal-assisted-4-16 edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-18
/cc @rccrdpccl @gamli75

Summary by CodeRabbit

• New Features

  • Refreshed available OS and release image catalogs with newer OpenShift versions across supported architectures.

• Bug Fixes

  • Corrected OpenShift 5.0 image references so they now point to the expected pre-release RHCOS artifacts.
  • Updated several release image entries to newer patch versions, including the default 4.22 option.

[openshift-ci-robot]

@andrej1991: This pull request explicitly references no jira issue.

Details

In response to this:

OpenShift updates: 4.22.0 -> 4.22.2, 4.22.0-multi -> 4.22.2-multi, 4.20.24 -> 4.20.26, 4.20.24-multi -> 4.20.26-multi, 4.19.33-multi -> 4.19.35-multi, 4.18.43-multi -> 4.18.45-multi, 4.19.33 -> 4.19.35, 4.16.63-multi -> 4.16.64-multi, 4.21.19 -> 4.21.21, 4.18.43 -> 4.18.45, 4.16.63 -> 4.16.64, 4.21.19-multi -> 4.21.21-multi
RHCOS updates: 4.22.0 -> 5.0.0-ec.3

/test edge-e2e-metal-assisted-5-0 edge-e2e-metal-assisted-4-19 edge-e2e-metal-assisted-4-21 edge-e2e-metal-assisted-4-22 edge-e2e-metal-assisted-4-16 edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-18
/cc @rccrdpccl @gamli75

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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 86c1a317-1605-4ef5-9aee-4343e29cb089

📥 Commits

Reviewing files that changed from the base of the PR and between 08dd374 and 3d41bfa.

📒 Files selected for processing (8)

• config/manager/manager.yaml
• config/samples/agent-install.openshift.io_v1beta1_agentserviceconfig.yaml
• data/default_os_images.json
• data/default_release_images.json
• deploy/olm-catalog/manifests/assisted-service-operator.clusterserviceversion.yaml
• deploy/podman/configmap.yml
• internal/common/test_versions_generated.go
• openshift/template.yaml

---

Walkthrough

Two image catalog updates are propagated across all deployment artifacts: (1) OpenShift 5.0 OS image URLs are corrected from 4.22.0-based paths to pre-release/5.0.0-ec.3 paths for all CPU architectures, and (2) OCP release image tags for versions 4.16 through 4.22 are bumped to newer patch versions. Both changes are reflected in data files, deployment configs, OLM manifests, and generated test fixtures.

Changes

Image Catalog Updates

Layer / File(s)	Summary
RHCOS 5.0 OS image URL correction data/default_os_images.json, config/manager/manager.yaml, config/samples/agent-install.openshift.io_v1beta1_agentserviceconfig.yaml, deploy/olm-catalog/manifests/assisted-service-operator.clusterserviceversion.yaml, deploy/podman/configmap.yml, openshift/template.yaml, internal/common/test_versions_generated.go	The openshift_version: "5.0" OS image URLs for x86_64, arm64, ppc64le, and s390x are changed from 4.22/4.22.0-based paths to rhcos/pre-release/5.0.0-ec.3 paths uniformly across all config surfaces and the generated test lookup table.
OCP release image tag bumps (4.16–4.22) data/default_release_images.json, deploy/podman/configmap.yml, openshift/template.yaml, internal/common/test_versions_generated.go	Release image url and version fields are bumped for OCP 4.16 (63→64), 4.18 (43→45), 4.19 (33→35), 4.20 (24→26), 4.21 (19→21), and 4.22 (0→2) across x86_64, arm64, and multi architectures, including the generated test fixtures.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

size/L

Suggested reviewers

• jhernand
• yoavsc0302

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description gives a version-update summary and test commands, but it omits the template's issue, motivation, environment, and checklist sections.	Add the missing sections: linked issue(s) or note none, motivation/context, impacted environments, and complete the testing/checklist items.

✅ Passed checks (14 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is specific and matches the version-bump changes, though it includes extra noise like NO-ISSUE and [master].
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	Only config/data/generated lookup files changed; no Ginkgo test titles or test files were added or edited.
Test Structure And Quality	✅ Passed	PR only changes config/data/generated version tables; no Ginkgo It/Eventually blocks or test setup/cleanup code were modified.
Microshift Test Compatibility	✅ Passed	No new Ginkgo tests were added; the touched files are manifests and generated lookup tables, with no MicroShift-sensitive test code.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo/e2e tests were added; the diff only updates config/data/version tables, so there are no SNO-specific assumptions to review.
Topology-Aware Scheduling Compatibility	✅ Passed	Only image/version catalog values changed; no node selectors, affinity, topology spread, or topology-aware replica logic was added.
Ote Binary Stdout Contract	✅ Passed	PASS: The PR only updates YAML/JSON tables and a generated Go lookup file; no main/init/TestMain/suite setup or stdout writes were present.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added; the changed files are config/generated image tables only, with no It/Describe/Context/When blocks.
No-Weak-Crypto	✅ Passed	Touched files are catalog/data updates only; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons were found.
Container-Privileges	✅ Passed	No touched manifest adds privileged/root settings; scans found allowPrivilegeEscalation only false and no hostPID/hostNetwork/hostIPC/SYS_ADMIN.
No-Sensitive-Data-In-Logs	✅ Passed	Patch only updates OS/release image URLs and versions; no new log statements or secret-bearing log fields were added.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[andrej1991]

/test verify-generated-code

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: andrej1991
Once this PR has been reviewed and has the lgtm label, please assign ori-amizur 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:

• OWNERS

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