Skip to content

Bump UPI image refs to 4.22#78984

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
patrickdillon:update-oc
May 8, 2026
Merged

Bump UPI image refs to 4.22#78984
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
patrickdillon:update-oc

Conversation

@patrickdillon
Copy link
Copy Markdown
Contributor

@patrickdillon patrickdillon commented May 7, 2026

Bump upi installer image version to 4.22. Particularly to pick up a bug fix in oc in 4.22 to filter tech preview credentials requests manifests.

Also needs openshift/installer#10538 but merge order doesn't matter.

Overview

Updates UPI (User Provisioned Infrastructure) installer step definitions in the OpenShift CI configuration to use OpenShift version 4.22. This brings the CI testing infrastructure in line with a bug fix in the oc tool that filters tech preview credentials requests manifests.

Changes

Four IPI installation step configurations in the CI step registry were updated to target OpenShift 4.22:

  • ipi-install-heterogeneous: Updated from 4.21 to 4.22
  • ipi-install-monitoringpvc: Updated from 4.12 to 4.22
  • ipi-install-post-featureset: Updated from 4.14 to 4.22
  • ipi-install-post-monitoringpvc: Updated from 4.12 to 4.22

Each update is a single-line change to the version reference in the respective step's configuration manifest. No functional logic or command definitions were modified.

Impact

These changes affect the CI infrastructure for testing OpenShift installer components. By updating to 4.22, the CI will use a newer version of the installer tooling in test workflows, enabling the bug fix for handling tech preview credentials that was introduced in that version.

Bump upi installer image version to 4.22. Particularly to pick up
a bug fix in oc in 4.22 to filter tech preview credentials
requests manifests.
@openshift-ci openshift-ci Bot requested review from philipgough and stbenjam May 7, 2026 14:57
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 7, 2026

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: 4ce3e6cb-f23f-4b86-999a-b2d77ebe52ed

📥 Commits

Reviewing files that changed from the base of the PR and between aad3ad3 and a66fbf4.

📒 Files selected for processing (4)
  • ci-operator/step-registry/ipi/install/heterogeneous/ipi-install-heterogeneous-ref.yaml
  • ci-operator/step-registry/ipi/install/monitoringpvc/ipi-install-monitoringpvc-ref.yaml
  • ci-operator/step-registry/ipi/install/post/featureset/ipi-install-post-featureset-ref.yaml
  • ci-operator/step-registry/ipi/install/post/monitoringpvc/ipi-install-post-monitoringpvc-ref.yaml

Walkthrough

Four CI operator step registry YAML files are updated to reference OpenShift version 4.22 instead of earlier versions (4.21, 4.12, and 4.14). Each file contains a single version reference update in its image configuration.

Changes

OpenShift Version Upgrade to 4.22

Layer / File(s) Summary
Configuration Updates
ci-operator/step-registry/ipi/install/heterogeneous/ipi-install-heterogeneous-ref.yaml, ci-operator/step-registry/ipi/install/monitoringpvc/ipi-install-monitoringpvc-ref.yaml, ci-operator/step-registry/ipi/install/post/featureset/ipi-install-post-featureset-ref.yaml, ci-operator/step-registry/ipi/install/post/monitoringpvc/ipi-install-post-monitoringpvc-ref.yaml
Version references unified to OpenShift 4.22 across heterogeneous install, monitoring PVC, and post-install feature set step definitions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Bump UPI image refs to 4.22' accurately describes the main change in the pull request - updating multiple UPI/IPI installer image references from various versions 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 This PR contains only YAML CI/CD configuration files with version updates. No Ginkgo test files are present, so the stable test names check is not applicable.
Test Structure And Quality ✅ Passed The custom check targets Ginkgo BDD test code. This PR contains only YAML config changes and standard Go unit tests, not Ginkgo tests. Check is not applicable.
Microshift Test Compatibility ✅ Passed PR does not add new Ginkgo e2e tests. It only modifies CI step registry YAML files to bump OpenShift installer image version to 4.22. The MicroShift test compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR contains no Ginkgo e2e tests. All changes are version updates in CI operator step registry YAML config files. The SNO check only applies when new tests are added.
Topology-Aware Scheduling Compatibility ✅ Passed PR updates CI/CD step registry configs (UPI installer image version bumps). Not deployment manifests, operator code, or controllers deployed to clusters. No scheduling constraints introduced.
Ote Binary Stdout Contract ✅ Passed PR contains only YAML configuration changes updating image versions. OTE Binary Stdout Contract applies to code changes. No code modifications present.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only updates image version references in YAML configs. No new Ginkgo e2e tests are added, so the 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

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 7, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 7, 2026

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

@patrickdillon
Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@patrickdillon: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Copy link
Copy Markdown
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 7, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon, tthvo

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:

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

@patrickdillon
Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@patrickdillon: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 8, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit f2c1f63 into openshift:main May 8, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants