Skip to content

Use quay-approvers OWNERS_ALIASES for Quay step registry#80125

Merged
openshift-merge-bot[bot] merged 3 commits into
openshift:mainfrom
redhat-chai-bot:06042011-bot-changes
Jun 8, 2026
Merged

Use quay-approvers OWNERS_ALIASES for Quay step registry#80125
openshift-merge-bot[bot] merged 3 commits into
openshift:mainfrom
redhat-chai-bot:06042011-bot-changes

Conversation

@redhat-chai-bot
Copy link
Copy Markdown
Contributor

@redhat-chai-bot redhat-chai-bot commented Jun 4, 2026

Summary

Adds a quay-approvers alias to OWNERS_ALIASES and updates the two root OWNERS files in ci-operator/step-registry/quay/ and ci-operator/step-registry/quay-tests/ to reference the alias instead of inlining 10 individual GitHub usernames.

What changed

  • OWNERS_ALIASES: Added quay-approvers alias with 10 team members: aroyoredhat, BillDett, cubismod, HammerMeetNail, jbpratt, kleesc, lechuk47, LiZhang19817, sunandadadi, syed
  • ci-operator/step-registry/quay/OWNERS: Replaced inline user list with quay-approvers alias reference
  • ci-operator/step-registry/quay-tests/OWNERS: Same change

Why

All 85 OWNERS files across the Quay step registry directories had identical content (10 hardcoded usernames). The 83 subdirectory files are symlinks to ../OWNERS, so updating the two root OWNERS files to use the alias automatically propagates the change everywhere.

Future roster changes now only require updating the quay-approvers alias definition in OWNERS_ALIASES — one PR instead of editing individual OWNERS files.

Summary by CodeRabbit

This PR centralizes and standardizes ownership for the Quay step-registry in the OpenShift CI configuration by introducing an OWNERS alias and switching many Quay-related OWNER/CI metadata entries to use it.

What's changing:

  • Adds a new OWNERS_ALIASES entry "quay-approvers" containing the Quay approver GitHub usernames (alias adjusted in commits to match quay/quay OWNERS — 12 members after the update).
  • Replaces inline approver/reviewer lists in the two root Quay OWNERS files (ci-operator/step-registry/quay/OWNERS and ci-operator/step-registry/quay-tests/OWNERS) with the single quay-approvers alias.
  • Regenerates registry metadata so numerous ci-operator step-registry metadata and workflow reference files (the Quay step-registry and many quay-tests metadata JSON/YAML files) now reference quay-approvers for owners.approvers and owners.reviewers instead of duplicated per-file username lists.

Why it matters (impact on CI/infrastructure):

  • The Quay step-registry contains many OWNERS entries (85 total; most are symlinked to the two root OWNERS). By centralizing the roster into a single OWNERS_ALIASES entry, maintainers only need to update the alias in one place when the approver roster changes, reducing maintenance effort and ensuring consistent approver/reviewer configuration across all Quay step-registry CI jobs and metadata.
  • A registry metadata regeneration commit is included so Prow/job metadata and CI references reflect the new alias usage.

Other notes:

  • The commits include an adjustment to the alias members to align with quay/quay OWNERS (adds and removes specific usernames) and a metadata regeneration commit to apply the alias change across CI metadata.

Adds a quay-approvers alias to OWNERS_ALIASES and updates the two
root OWNERS files in ci-operator/step-registry/quay/ and
ci-operator/step-registry/quay-tests/ to reference the alias instead
of inlining 10 individual GitHub usernames.

All 83 subdirectory OWNERS files are symlinks to ../OWNERS and
automatically pick up the change. Future roster changes only require
updating the alias definition in one place.
@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jun 4, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 4, 2026

Hi @redhat-chai-bot. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 4, 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: 81bff4bf-2cb7-479d-98c4-9e9c97308997

📥 Commits

Reviewing files that changed from the base of the PR and between 5b4cd7b and f9ed6c5.

📒 Files selected for processing (78)
  • OWNERS_ALIASES
  • ci-operator/step-registry/quay-tests/aws-ipi-disconnected-private-deprovision/quay-tests-aws-ipi-disconnected-private-deprovision-chain.metadata.json
  • ci-operator/step-registry/quay-tests/aws-ipi-disconnected-private-provision/quay-tests-aws-ipi-disconnected-private-provision-chain.metadata.json
  • ci-operator/step-registry/quay-tests/azure/app-deletion/quay-tests-azure-app-deletion-ref.metadata.json
  • ci-operator/step-registry/quay-tests/azure/app-registrations/quay-tests-azure-app-registrations-ref.metadata.json
  • ci-operator/step-registry/quay-tests/cso-qe-test/quay-tests-cso-qe-test-ref.metadata.json
  • ci-operator/step-registry/quay-tests/cucushift-installer-rehearse-aws-ipi-operator/quay-tests-cucushift-installer-rehearse-aws-ipi-operator-workflow.metadata.json
  • ci-operator/step-registry/quay-tests/cucushift-installer-rehearse-aws-ipi/quay-tests-cucushift-installer-rehearse-aws-ipi-workflow.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-omr/quay-tests-deploy-omr-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-aws-rds-postgresql/quay-tests-deploy-quay-aws-rds-postgresql-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-aws-s3/quay-tests-deploy-quay-aws-s3-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-azure/quay-tests-deploy-quay-azure-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-custom-image/quay-tests-deploy-quay-custom-image-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-gcp/quay-tests-deploy-quay-gcp-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-ibmcos/quay-tests-deploy-quay-ibmcos-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-netapp-storagegrid/quay-tests-deploy-quay-netapp-storagegrid-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-odf/quay-tests-deploy-quay-odf-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deprovisioning-aws-gcp-azure-storage-buckets/quay-tests-deprovisioning-aws-gcp-azure-storage-buckets-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deprovisioning-quay-aws-rds-postgresql/quay-tests-deprovisioning-quay-aws-rds-postgresql-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deprovisioning-quay-security-testing/quay-tests-deprovisioning-quay-security-testing-ref.metadata.json
  • ci-operator/step-registry/quay-tests/enable-quay-catalogsource/quay-tests-enable-quay-catalogsource-ref.metadata.json
  • ci-operator/step-registry/quay-tests/ipi-conf-mirror/quay-tests-ipi-conf-mirror-ref.metadata.json
  • ci-operator/step-registry/quay-tests/mirror-images-oc-adm/quay-tests-mirror-images-oc-adm-chain.metadata.json
  • ci-operator/step-registry/quay-tests/mirror-images-oc-adm/quay-tests-mirror-images-oc-adm-ref.metadata.json
  • ci-operator/step-registry/quay-tests/omr-install-ocp/quay-tests-omr-install-ocp-ref.metadata.json
  • ci-operator/step-registry/quay-tests/omr-mirror-ocp/quay-tests-omr-mirror-ocp-ref.metadata.json
  • ci-operator/step-registry/quay-tests/provisioning-omr-disconnected/quay-tests-provisioning-omr-disconnected-ref.metadata.json
  • ci-operator/step-registry/quay-tests/provisioning-quay-security-testing/quay-tests-provisioning-quay-security-testing-ref.metadata.json
  • ci-operator/step-registry/quay-tests/qbo-qe-test/quay-tests-qbo-qe-test-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay-acs/quay-tests-quay-acs-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay-e2e-test/quay-tests-quay-e2e-test-chain.metadata.json
  • ci-operator/step-registry/quay-tests/quay-interop-test/quay-tests-quay-interop-test-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay-oci-conformance-test/quay-tests-quay-oci-conformance-test-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-operator/quay-tests-quay-deploy-operator-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-registry-awss3cloudfront/quay-tests-quay-deploy-registry-awss3cloudfront-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-registry-awssts/quay-tests-quay-deploy-registry-awssts-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-registry-builder/quay-tests-quay-deploy-registry-builder-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-registry-ceph/quay-tests-quay-deploy-registry-ceph-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-registry-gsql/quay-tests-quay-deploy-registry-gsql-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-registry-noobaa/quay-tests-quay-deploy-registry-noobaa-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-registry-unmanaged-tls/quay-tests-quay-deploy-registry-unmanaged-tls-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quayio/quay-tests-quayio-ref.metadata.json
  • ci-operator/step-registry/quay-tests/recycle-omr/quay-tests-recycle-omr-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/deprovisioning/aws-unmanaged-component/quay-tests-resource-deprovisioning-aws-unmanaged-component-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/deprovisioning/gcp-sql/quay-tests-resource-deprovisioning-gcp-sql-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/aws-unmanaged-component/quay-tests-resource-provisioning-aws-unmanaged-component-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/builder/quay-tests-resource-provisioning-builder-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/gcp-sql/quay-tests-resource-provisioning-gcp-sql-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/storage/aws-sts-s3/quay-tests-resource-provisioning-storage-aws-sts-s3-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/storage/ceph/quay-tests-resource-provisioning-storage-ceph-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/storage/odf/quay-tests-resource-provisioning-storage-odf-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/storage/s3cloudfront/quay-tests-resource-provisioning-storage-s3cloudfront-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/tls/quay-tests-resource-provisioning-tls-ref.metadata.json
  • ci-operator/step-registry/quay-tests/scan-quay-images/quay-tests-scan-quay-images-ref.metadata.json
  • ci-operator/step-registry/quay-tests/stage-quay-io-old-ui/quay-tests-stage-quay-io-old-ui-ref.metadata.json
  • ci-operator/step-registry/quay-tests/stage-quay-io/quay-tests-stage-quay-io-ref.metadata.json
  • ci-operator/step-registry/quay-tests/stagequayio/quay-tests-stagequayio-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test-quay-dast/quay-tests-test-quay-dast-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test-quay-e2e/quay-tests-test-quay-e2e-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test-quay-newui-stress/quay-tests-test-quay-newui-stress-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test-quay-newui/quay-tests-test-quay-newui-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test-quay-playwright/quay-tests-test-quay-playwright-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test/performance/quay-tests-test-performance-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test/quay-api/quay-tests-test-quay-api-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test/quay-operator/quay-tests-test-quay-operator-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test/quay-upgrade/quay-tests-test-quay-upgrade-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test/stage-performance/quay-tests-test-stage-performance-ref.metadata.json
  • ci-operator/step-registry/quay/create-admin-user/quay-create-admin-user-ref.metadata.json
  • ci-operator/step-registry/quay/create-admin/quay-create-admin-ref.metadata.json
  • ci-operator/step-registry/quay/enable-quay-bridge-operator/quay-enable-quay-bridge-operator-ref.metadata.json
  • ci-operator/step-registry/quay/gather/quay-gather-ref.metadata.json
  • ci-operator/step-registry/quay/install-ocs-operator/quay-install-ocs-operator-ref.metadata.json
  • ci-operator/step-registry/quay/install-odf-operator/quay-install-odf-operator-ref.metadata.json
  • ci-operator/step-registry/quay/install-operator-bundle/quay-install-operator-bundle-ref.metadata.json
  • ci-operator/step-registry/quay/install-quay-operator/quay-install-quay-operator-ref.metadata.json
  • ci-operator/step-registry/quay/install-quay/quay-install-quay-ref.metadata.json
  • ci-operator/step-registry/quay/test-chainsaw/quay-test-chainsaw-ref.metadata.json
  • ci-operator/step-registry/quay/test-mirror-image/quay-test-mirror-image-ref.metadata.json
✅ Files skipped from review due to trivial changes (19)
  • ci-operator/step-registry/quay-tests/stage-quay-io/quay-tests-stage-quay-io-ref.metadata.json
  • ci-operator/step-registry/quay/install-odf-operator/quay-install-odf-operator-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay/deploy-registry-unmanaged-tls/quay-tests-quay-deploy-registry-unmanaged-tls-ref.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/gcp-sql/quay-tests-resource-provisioning-gcp-sql-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deprovisioning-quay-security-testing/quay-tests-deprovisioning-quay-security-testing-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quayio/quay-tests-quayio-ref.metadata.json
  • ci-operator/step-registry/quay-tests/omr-install-ocp/quay-tests-omr-install-ocp-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-netapp-storagegrid/quay-tests-deploy-quay-netapp-storagegrid-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-omr/quay-tests-deploy-omr-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test-quay-newui-stress/quay-tests-test-quay-newui-stress-ref.metadata.json
  • ci-operator/step-registry/quay-tests/qbo-qe-test/quay-tests-qbo-qe-test-ref.metadata.json
  • ci-operator/step-registry/quay-tests/deploy-quay-aws-s3/quay-tests-deploy-quay-aws-s3-ref.metadata.json
  • ci-operator/step-registry/quay/install-quay/quay-install-quay-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test/quay-api/quay-tests-test-quay-api-ref.metadata.json
  • ci-operator/step-registry/quay-tests/quay-e2e-test/quay-tests-quay-e2e-test-chain.metadata.json
  • ci-operator/step-registry/quay/install-operator-bundle/quay-install-operator-bundle-ref.metadata.json
  • ci-operator/step-registry/quay-tests/test/quay-operator/quay-tests-test-quay-operator-ref.metadata.json
  • ci-operator/step-registry/quay-tests/mirror-images-oc-adm/quay-tests-mirror-images-oc-adm-chain.metadata.json
  • ci-operator/step-registry/quay-tests/resource/provisioning/aws-unmanaged-component/quay-tests-resource-provisioning-aws-unmanaged-component-ref.metadata.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • OWNERS_ALIASES

Walkthrough

Add a new quay-approvers alias and update OWNERS and CI/step-registry metadata to replace explicit approver/reviewer username lists with that alias across quay-related files.

Changes

Quay Approvers Alias Consolidation

Layer / File(s) Summary
Define quay-approvers alias
OWNERS_ALIASES
Insert a new quay-approvers alias block listing the designated approver handles.
Adopt quay-approvers across OWNERS & CI metadata
ci-operator/step-registry/quay-tests/OWNERS, ci-operator/step-registry/quay/OWNERS, ci-operator/step-registry/quay-tests/... (many metadata files)
Replace explicit approvers and reviewers username arrays with the single quay-approvers alias reference in OWNERS and CI/step-registry metadata files.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

lgtm

Suggested reviewers

  • deepsm007
🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title 'Use quay-approvers OWNERS_ALIASES for Quay step registry' accurately describes the main change: introducing and using the quay-approvers alias in the Quay step registry OWNERS files.
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 only OWNERS and metadata configuration files, no Ginkgo test code. The check for stable/deterministic test names is not applicable.
Test Structure And Quality ✅ Passed PR modifies only configuration files (OWNERS_ALIASES, OWNERS, metadata.json), not Ginkgo test code. The test quality check is not applicable to this PR.
Microshift Test Compatibility ✅ Passed This PR only modifies configuration files (OWNERS_ALIASES, OWNERS, and .metadata.json) and does not add any new Ginkgo e2e test code, so the MicroShift Test Compatibility check does not apply.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR contains no new Ginkgo e2e tests; it only updates OWNERS configuration and CI metadata. The SNO test compatibility check does not apply to administrative/configuration-only changes.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only OWNERS_ALIASES, OWNERS files, and CI metadata—no deployment manifests, operator code, or scheduling constraints are introduced.
Ote Binary Stdout Contract ✅ Passed PR modifies only configuration/metadata files (OWNERS_ALIASES, OWNERS, .metadata.json). No executable code or stdout operations are present, so the OTE Binary Stdout Contract check is not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR contains no new Ginkgo e2e tests; only modifies OWNERS and metadata configuration files.
No-Weak-Crypto ✅ Passed PR contains only configuration changes (OWNERS aliases and metadata updates) with no cryptographic code added, modified, or executed.
Container-Privileges ✅ Passed PR modifies only OWNERS configuration and CI metadata files, not K8s/container manifests; check for privileged configurations is not applicable.
No-Sensitive-Data-In-Logs ✅ Passed PR only modifies configuration/metadata files with public GitHub usernames; no logging code or sensitive data (passwords, tokens, API keys) exposed.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci Bot requested review from deepsm007 and smg247 June 4, 2026 20:15
@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jun 4, 2026
Adds harishsurf, Marcusk19, shaonrh, sridipta. Removes BillDett and
syed. The alias now has 12 members matching the cleaned-up quay/quay
OWNERS file.
@jbpratt
Copy link
Copy Markdown
Contributor

jbpratt commented Jun 4, 2026

/ok-to-test
/lgtm

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 4, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2026
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@redhat-chai-bot: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

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.

@jbpratt
Copy link
Copy Markdown
Contributor

jbpratt commented Jun 8, 2026

/assign @deepsm007 @smg247

@deepsm007
Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci Bot commented Jun 8, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, jbpratt, redhat-chai-bot

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

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

openshift-ci Bot commented Jun 8, 2026

@redhat-chai-bot: 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-merge-bot openshift-merge-bot Bot merged commit 0362971 into openshift:main Jun 8, 2026
10 checks passed
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@openshift-ci[bot]: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants