Skip to content

Update Prow as needed#79277

Open
openshift-bot wants to merge 1 commit into
openshift:mainfrom
openshift-bot:autobump
Open

Update Prow as needed#79277
openshift-bot wants to merge 1 commit into
openshift:mainfrom
openshift-bot:autobump

Conversation

@openshift-bot
Copy link
Copy Markdown
Contributor

@openshift-bot openshift-bot commented May 13, 2026

us-docker.pkg.dev/k8s-infra-prow/images/ changes: kubernetes-sigs/prow@77c4e05...f65e1b3 (2026‑05‑08 → 2026‑05‑12)

No gcr.io/k8s-staging-boskos/ changes.

No gcr.io/k8s-staging-test-infra changes.

Nobody is currently oncall, so falling back to Blunderbuss.
/pj-rehearse auto-ack
/cc @openshift/test-platform

Prow Infrastructure Update

This PR updates the OpenShift CI infrastructure to use a newer build of Prow components. All container image tags for Prow services are bumped from v20260508-77c4e0541 to v20260512-f65e1b3c3, corresponding to upstream Prow changes from May 8–12, 2026.

Scope of Changes

Production and Staging Deployments: Updates image tags across both production (clusters/app.ci/prow/03_deployment/) and staging (clusters/app.ci/prow/staging/) deployment manifests for 16+ Prow components, including:

  • Core services: cherrypick, crier, deck, ghproxy, hook, sinker, tide, tot
  • Job management: horologium, prow-controller-manager, needs-rebase, refresh, statusreconciler
  • Utility components: exporter, gangway, qe-private-deck

Utility Images: Updates references to shared Prow utility images (clonerefs, entrypoint, initupload, sidecar) in:

  • Production Prow configuration (core-services/prow/02_config/_config.yaml)
  • Staging Prow configuration (clusters/app.ci/prow/staging/prow-config.yaml)

Build Tooling: Updates image variables in hack/images.sh for the mkpj and mkpod image builders.

Image Mirroring: Updates the image mirroring configuration to reference the newer clonerefs build tag.

Makefile: Updates the checkconfig target to use the newer image tag for configuration validation.

Impact

This is a routine maintenance update that keeps OpenShift's Prow infrastructure in sync with upstream Prow development. All updates are consistent image tag changes with no modifications to deployment configuration, resource specifications, or operational behavior.

us-docker.pkg.dev/k8s-infra-prow/images/ changes: kubernetes-sigs/prow@77c4e05...f65e1b3 (2026‑05‑08 → 2026‑05‑12)

No gcr.io/k8s-staging-boskos/ changes.

No gcr.io/k8s-staging-test-infra changes.
@openshift-ci openshift-ci Bot requested a review from a team May 13, 2026 22:04
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 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: ada2fae1-6208-4f07-b3e3-ca518878cbc5

📥 Commits

Reviewing files that changed from the base of the PR and between 4e8112c and 02bafc9.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/infra-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/release/openshift-release-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (25)
  • Makefile
  • clusters/app.ci/prow/03_deployment/cherrypick.yaml
  • clusters/app.ci/prow/03_deployment/crier.yaml
  • clusters/app.ci/prow/03_deployment/deck.yaml
  • clusters/app.ci/prow/03_deployment/exporter.yaml
  • clusters/app.ci/prow/03_deployment/gangway.yaml
  • clusters/app.ci/prow/03_deployment/ghproxy.yaml
  • clusters/app.ci/prow/03_deployment/hook.yaml
  • clusters/app.ci/prow/03_deployment/horologium.yaml
  • clusters/app.ci/prow/03_deployment/needs_rebase.yaml
  • clusters/app.ci/prow/03_deployment/prow-controller-manager.yaml
  • clusters/app.ci/prow/03_deployment/qe_private_deck.yaml
  • clusters/app.ci/prow/03_deployment/refresh.yaml
  • clusters/app.ci/prow/03_deployment/sinker.yaml
  • clusters/app.ci/prow/03_deployment/statusreconciler.yaml
  • clusters/app.ci/prow/03_deployment/tide.yaml
  • clusters/app.ci/prow/03_deployment/tot.yaml
  • clusters/app.ci/prow/staging/crier.yaml
  • clusters/app.ci/prow/staging/deck.yaml
  • clusters/app.ci/prow/staging/ghproxy.yaml
  • clusters/app.ci/prow/staging/prow-config.yaml
  • clusters/app.ci/prow/staging/sinker.yaml
  • core-services/image-mirroring/_config.yaml
  • core-services/prow/02_config/_config.yaml
  • hack/images.sh

Walkthrough

Container image tags are updated from v20260508-77c4e0541 to v20260512-f65e1b3c3 across build tools, Kubernetes deployment manifests, and Prow configuration files. No functionality or logic is modified.

Changes

Container Image Tag Updates

Layer / File(s) Summary
Build tooling image tags
Makefile, hack/images.sh
Build tool references for checkconfig, mkpj, and mkpod images are updated to the new tag version.
Production deployment manifests
clusters/app.ci/prow/03_deployment/cherrypick.yaml, crier.yaml, deck.yaml, exporter.yaml, gangway.yaml, ghproxy.yaml, hook.yaml, horologium.yaml, needs_rebase.yaml, prow-controller-manager.yaml, qe_private_deck.yaml, refresh.yaml, sinker.yaml, statusreconciler.yaml, tide.yaml, tot.yaml
Container image tags across 16 production Prow service deployments are updated to the newer version.
Staging deployment manifests and utilities
clusters/app.ci/prow/staging/crier.yaml, deck.yaml, ghproxy.yaml, prow-config.yaml, sinker.yaml
Staging Prow service deployments and their utility image references in the Prow configuration are updated to match the new tag.
Core services configuration
core-services/image-mirroring/_config.yaml, core-services/prow/02_config/_config.yaml
Image mirroring configuration and default Prow decoration utility image references are updated to the new tag version.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

lgtm, rehearsals-ack

Suggested reviewers

  • mmazur
  • geoberle
  • raelga
🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Update Prow as needed' is vague and generic, using non-descriptive language that doesn't convey meaningful information about the specific changes in the changeset. Consider a more specific title like 'Bump Prow images to v20260512-f65e1b3c3' that clearly describes what is being updated and to which version.
✅ Passed checks (11 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
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 code. All changes are infrastructure configuration updates (container image tags, manifests). Check not applicable.
Test Structure And Quality ✅ Passed Custom check for Ginkgo test structure is not applicable. PR contains only infrastructure configuration changes (YAML manifests, Makefile, shell scripts) with no test files.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests are added in this PR. Only container image versions are updated in Kubernetes manifests and configuration files. The MicroShift compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No new Ginkgo e2e tests are added in this PR. Changes are limited to container image tag updates in deployment manifests and configuration files. SNO compatibility check not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR only updates Prow container image tags from v20260508 to v20260512. No scheduling constraints, affinity rules, replica counts, or topology-related configurations were changed.
Ote Binary Stdout Contract ✅ Passed Check not applicable. PR modifies only configuration files (YAML, Makefile, shell script) to update container image tags. No source code changes. Repository contains no OTE binary code.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR updates container image tags only. No new Ginkgo e2e tests added. IPv6/disconnected network compatibility check 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 13, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@openshift-bot: 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-release-main-config openshift/release presubmit Presubmit changed
periodic-openshift-release-main-accept-invitations-merge-robot N/A periodic Periodic changed
periodic-openshift-release-main-accept-invitations-ci-robot N/A periodic Periodic changed
periodic-openshift-release-main-accept-invitations-cherrypick-robot N/A periodic Periodic 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-merge-bot
Copy link
Copy Markdown
Contributor

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 13, 2026

@openshift-bot: 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/rehearse/periodic-openshift-release-main-accept-invitations-merge-robot 02bafc9 link unknown /pj-rehearse periodic-openshift-release-main-accept-invitations-merge-robot
ci/rehearse/periodic-openshift-release-main-accept-invitations-ci-robot 02bafc9 link unknown /pj-rehearse periodic-openshift-release-main-accept-invitations-ci-robot

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant