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

[danmanor]

OpenShift updates: 4.22.0-ec.5-multi -> 4.22.0-rc.0-multi, 4.22.0-ec.5 -> 4.22.0-rc.0, 4.20.18-multi -> 4.20.19-multi, 4.20.18 -> 4.20.19, 4.21.10-multi -> 4.21.11-multi, 4.18.37 -> 4.18.38, 4.21.10 -> 4.21.11, 4.18.37-multi -> 4.18.38-multi
RHCOS updates:

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

Summary by CodeRabbit

• Chores
  • Updated OpenShift release image versions across multiple releases: 4.18 to 4.18.38, 4.20 to 4.20.19, 4.21 to 4.21.11, and 4.22 to 4.22.0-rc.0 for all supported architectures (x86_64, aarch64, multi).

[openshift-ci-robot]

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

Details

In response to this:

OpenShift updates: 4.22.0-ec.5-multi -> 4.22.0-rc.0-multi, 4.22.0-ec.5 -> 4.22.0-rc.0, 4.20.18-multi -> 4.20.19-multi, 4.20.18 -> 4.20.19, 4.21.10-multi -> 4.21.11-multi, 4.18.37 -> 4.18.38, 4.21.10 -> 4.21.11, 4.18.37-multi -> 4.18.38-multi
RHCOS updates:

/test edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-21 edge-e2e-metal-assisted-4-22 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]

Walkthrough

Updates OpenShift release image versions and URLs across multiple configuration files. Version 4.18 incremented to 4.18.38, 4.20 to 4.20.19, 4.21 to 4.21.11, and 4.22 transitioned from 4.22.0-ec.5 to 4.22.0-rc.0. Also removes trailing newline from one data file.

Changes

Cohort / File(s)	Summary
OS Images Metadata data/default_os_images.json	Removes trailing newline at end of file.
Release Image Updates data/default_release_images.json, deploy/podman/configmap.yml, openshift/template.yaml	Updates OpenShift release image versions and URLs for 4.18 (→4.18.38), 4.20 (→4.20.19), 4.21 (→4.21.11), and 4.22 (→4.22.0-rc.0) across x86_64, aarch64, and multi architectures.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description includes specific version updates but lacks required template sections like issue categorization, environment impact, testing approach, and completion checklist.	Fill in the description template sections: mark relevant issue type checkboxes, confirm environment impact, specify testing method, and complete the checklist items.

✅ Passed checks (11 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: bumping OpenShift versions across multiple release branches (4.18, 4.20, 4.21, 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 contains no Ginkgo test files or test name modifications, only configuration file updates.
Test Structure And Quality	✅ Passed	PR modifies only configuration and data files (JSON and YAML); no test code changes present, so Ginkgo test quality check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only modifies configuration and data files (JSON and YAML manifests); no new Ginkgo e2e tests are added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR modifies only configuration and data files (JSON/YAML) for OpenShift version updates with no new Ginkgo e2e tests added.
Topology-Aware Scheduling Compatibility	✅ Passed	PR contains only data-level version updates to OpenShift release configurations with no scheduling constraints, affinity rules, or topology-dependent logic.
Ote Binary Stdout Contract	✅ Passed	This pull request contains exclusively configuration and data file updates with no Go source code modifications.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This pull request does not add any new Ginkgo e2e tests. Changes are exclusively to configuration and data files, not test code.

_{✏️ 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 and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

openshift/template.yaml (1)

23-23: Consider generating this JSON from a single source of truth.

RELEASE_IMAGES is duplicated across data/default_release_images.json, deploy/podman/configmap.yml, and this template. Auto-generation would reduce drift risk on future bumps.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@openshift/template.yaml` at line 23, The release images JSON is duplicated
(seen as the value field in openshift/template.yaml and also in
data/default_release_images.json and deploy/podman/configmap.yml); create a
single source of truth (e.g., data/default_release_images.json) and change
openshift/template.yaml to reference or inject that file during build/templating
instead of hardcoding the JSON (replace the literal value in the value field
with a templated include or build-time substitution), and update any deployment
manifests (deploy/podman/configmap.yml) to consume the same generated artifact
so all consumers of RELEASE_IMAGES are produced from the same generator (or add
a small generation script invoked by CI/build to populate all three locations).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@openshift/template.yaml`:
- Line 23: The release images JSON is duplicated (seen as the value field in
openshift/template.yaml and also in data/default_release_images.json and
deploy/podman/configmap.yml); create a single source of truth (e.g.,
data/default_release_images.json) and change openshift/template.yaml to
reference or inject that file during build/templating instead of hardcoding the
JSON (replace the literal value in the value field with a templated include or
build-time substitution), and update any deployment manifests
(deploy/podman/configmap.yml) to consume the same generated artifact so all
consumers of RELEASE_IMAGES are produced from the same generator (or add a small
generation script invoked by CI/build to populate all three locations).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 1379b090-b5e1-46ac-8501-0732df686395

📥 Commits

Reviewing files that changed from the base of the PR and between c807774 and 28ea1d3.

📒 Files selected for processing (4)

• data/default_os_images.json
• data/default_release_images.json
• deploy/podman/configmap.yml
• openshift/template.yaml

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.34%. Comparing base (c807774) to head (28ea1d3).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10201   +/-   ##
=======================================
  Coverage   44.34%   44.34%           
=======================================
  Files         415      415           
  Lines       72770    72770           
=======================================
  Hits        32270    32270           
  Misses      37584    37584           
  Partials     2916     2916           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[openshift-ci]

@danmanor: 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danmanor, gamli75

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:

• OWNERS [danmanor,gamli75]

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