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

[danmanor]

OpenShift updates: 4.20.21 -> 4.20.22, 4.19.30-multi -> 4.19.31-multi, 4.14.63 -> 4.14.66, 4.16.61-multi -> 4.16.62-multi, 4.21.14-multi -> 4.21.15-multi, 4.18.40 -> 4.18.41, 4.20.21-multi -> 4.20.22-multi, 4.16.61 -> 4.16.62, 4.21.14 -> 4.21.15, 4.19.30 -> 4.19.31, 4.14.63-multi -> 4.14.66-multi, 4.18.40-multi -> 4.18.41-multi
RHCOS updates:

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

Summary by CodeRabbit

• Chores
  • Updated OpenShift release image references for versions 4.14 through 4.21 across multiple CPU architectures (x86_64, arm64, multi).

[openshift-ci-robot]

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

Details

In response to this:

OpenShift updates: 4.20.21 -> 4.20.22, 4.19.30-multi -> 4.19.31-multi, 4.14.63 -> 4.14.66, 4.16.61-multi -> 4.16.62-multi, 4.21.14-multi -> 4.21.15-multi, 4.18.40 -> 4.18.41, 4.20.21-multi -> 4.20.22-multi, 4.16.61 -> 4.16.62, 4.21.14 -> 4.21.15, 4.19.30 -> 4.19.31, 4.14.63-multi -> 4.14.66-multi, 4.18.40-multi -> 4.18.41-multi
RHCOS updates:

/test edge-e2e-metal-assisted-4-20 edge-e2e-metal-assisted-4-18 edge-e2e-metal-assisted-4-14 edge-e2e-metal-assisted-4-21 edge-e2e-metal-assisted-4-16 edge-e2e-metal-assisted-4-19
/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: 7b53c544-3ac6-4e3c-9740-96cf78e86fd0

📥 Commits

Reviewing files that changed from the base of the PR and between 963e8a7 and b51e523.

📒 Files selected for processing (3)

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

---

Walkthrough

Updates OpenShift release image references by advancing url and version tags across releases 4.14, 4.16, 4.18, 4.19, 4.20, and 4.21 for all CPU architecture variants. Changes are synchronized across the source data file and two downstream deployment configurations.

Changes

Release Image Catalog Updates

Layer / File(s)	Summary
Release image catalog data updates data/default_release_images.json	Updates url and version fields in the primary release image catalog for OpenShift 4.14, 4.16, 4.18, 4.19, 4.20, and 4.21 entries, covering all CPU architecture variants (x86_64, arm64, and multi).
Deployment configuration synchronization deploy/podman/configmap.yml, openshift/template.yaml	Propagates updated release image references from the catalog into ConfigMap and template resources that embed the release image metadata.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• openshift/assisted-service#10152: Both PRs update the same RELEASE_IMAGES source-of-truth data by bumping OpenShift 4.21 release image tags.
• openshift/assisted-service#10162: Both PRs update the same RELEASE_IMAGES mappings for OpenShift 4.19 across data/default_release_images.json and deployment configs.
• openshift/assisted-service#10284: Both PRs update the same OpenShift release image metadata with ocp-release tag bumping across the same three manifests.

Suggested labels

approved, size/M, lgtm

Suggested reviewers

• rccrdpccl
• gamli75

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description lacks required template sections: missing checkboxes for issue type, environment impact is marked 'None' (inconsistent with code changes), and key checklist items are incomplete or unchecked despite being applicable.	Complete the template by selecting appropriate issue type (Enhancement), marking code impact correctly, checking relevant testing/documentation items, and ensuring all checklist sections are properly addressed.

✅ Passed checks (11 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the main change: bumping OCP versions across multiple releases (4.20, 4.18, 4.14, 4.21, 4.16, 4.19), which matches the file modifications in the changeset.
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 definitions. All changes are in configuration/data files (JSON, ConfigMap YAML, template YAML) that update OpenShift release versions. Check is not applicable.
Test Structure And Quality	✅ Passed	PR contains no test files. Changes are limited to configuration files that update OpenShift release image references. Custom check for Ginkgo test code is not applicable.
Microshift Test Compatibility	✅ Passed	This PR contains only configuration file updates (OpenShift release image version bumps). No new Ginkgo e2e tests are added. The MicroShift Test Compatibility check applies only to new tests.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR updates OpenShift release versions in configuration files only. No new Ginkgo e2e tests are added, so SNO compatibility check does not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only updates release image version references in data/config files. No deployment manifests, operators, or controllers are added or modified, so the topology-aware scheduling check does not apply.
Ote Binary Stdout Contract	✅ Passed	PR only modifies data/config files (JSON/YAML). No process-level code, logging setup, or stdout writes are present. OTE Binary Stdout Contract check is not applicable.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only configuration/data files with OpenShift release version updates. No new Ginkgo e2e tests are added, so IPv6/disconnected network compatibility check is not applicable.

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danmanor

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]

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.32%. Comparing base (963e8a7) to head (b51e523).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #10335      +/-   ##
==========================================
- Coverage   44.32%   44.32%   -0.01%     
==========================================
  Files         417      417              
  Lines       72762    72762              
==========================================
- Hits        32253    32249       -4     
- Misses      37589    37592       +3     
- Partials     2920     2921       +1     

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[openshift-ci]

@danmanor: The following tests 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/edge-e2e-metal-assisted-4-16	b51e523	link	true	/test edge-e2e-metal-assisted-4-16
ci/prow/edge-subsystem-kubeapi-aws	b51e523	link	true	/test edge-subsystem-kubeapi-aws
ci/prow/edge-e2e-metal-assisted-4-22	b51e523	link	true	/test edge-e2e-metal-assisted-4-22
ci/prow/edge-e2e-metal-assisted-5-0	b51e523	link	true	/test edge-e2e-metal-assisted-5-0
ci/prow/e2e-agent-compact-ipv4	b51e523	link	true	/test e2e-agent-compact-ipv4
ci/prow/e2e-agent-compact-ipv4-iso-no-registry	b51e523	link	false	/test e2e-agent-compact-ipv4-iso-no-registry

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.