ci(quay-operator): promote master images by commit

[jbpratt]

Summary

Promote the Quay Operator master image and bundle to stable source-CI names. Keep the existing internal bundle name for job dependencies while publishing moving and commit-derived tags for external consumers.

Related Issue

NO-ISSUE: CI-only promotion wiring with no product or runtime behavior changes.

Changes

• Promote the operator as quay-operator under both latest and commit-derived tags.
• Promote the internal quay bundle as quay-operator-bundle under both latest and commit-derived tags.
• Regenerate master presubmit and postsubmit jobs with the bundle promotion target.

Testing

• make ci-operator-config
• make jobs WHAT=quay/quay-operator
• make ci-operator-checkconfig
• git diff --check

Notes

This changes only the master source-CI lane. Release-branch promotion remains follow-up work.

Summary by CodeRabbit

Updates the Quay Operator master source-CI promotion to publish stable quay-operator and quay-operator-bundle images with latest and commit-derived tags, while preserving the internal quay bundle name for job dependencies. Master presubmit and postsubmit jobs are regenerated accordingly; release branches are unaffected.

[coderabbitai]

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: 3b8f06cd-44da-4d83-a4fc-b2ae4946df50

📥 Commits

Reviewing files that changed from the base of the PR and between 7048642 and a360254.

⛔ Files ignored due to path filters (2)

• ci-operator/jobs/quay/quay-operator/quay-quay-operator-master-postsubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/quay/quay-operator/quay-quay-operator-master-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (1)

• ci-operator/config/quay/quay-operator/quay-quay-operator-master__ocp-latest.yaml

---

Walkthrough

The Quay promotion configuration now includes quay-operator-bundle: quay in additional_images and enables commit-based tagging for the quay promotion target.

Changes

Quay promotion

Layer / File(s)	Summary
Update Quay promotion target ci-operator/config/quay/quay-operator/quay-quay-operator-master__ocp-latest.yaml	The quay target promotes quay-operator-bundle: quay and sets tag_by_commit: true while retaining existing exclusions and tagging.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• openshift/release#82052: Updates related Quay promotion configuration to enable commit-based image tagging.

Suggested labels: lgtm, approved, rehearsals-ack

🚥 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 title is clear and matches the main change: promoting Quay Operator master images with commit-derived tagging.
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 only changes CI promotion/job YAML; no Ginkgo It/Describe/Context/When titles were added or modified.
Test Structure And Quality	✅ Passed	No Ginkgo test code was changed; the PR only updates ci-operator promotion/job YAML, so the test-structure checklist is not applicable.
Microshift Test Compatibility	✅ Passed	No new Ginkgo e2e tests or OpenShift API usage were added; only CI promotion/job YAML changed.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added; the diff only updates CI promotion/job YAML for Quay images and bundle targets.
Topology-Aware Scheduling Compatibility	✅ Passed	Only ci-operator promotion/job YAML changed; no deployment manifests, controllers, node selectors, affinity, or PDB/scheduling constraints were introduced.
Ote Binary Stdout Contract	✅ Passed	Only generated ci-operator/job YAML changed; no OTE binary source or suite setup code was modified, so no new stdout contract violation.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo tests were added; the PR only updates promotion/job targets, with no new IPv4 assumptions or external-connectivity test steps.
No-Weak-Crypto	✅ Passed	The patch only changes CI promotion/job targets; the diff and touched files contain no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB or custom crypto code.
Container-Privileges	✅ Passed	Diff only adds promotion/job targets; no privileged, host* , SYS_ADMIN, root, or allowPrivilegeEscalation fields appear in changed YAML.
No-Sensitive-Data-In-Logs	✅ Passed	Diff only changes CI promotion targets/tagging; no new log statements or sensitive data exposure were added.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@jbpratt: 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-quay-quay-operator-master-ocp-latest-images	quay/quay-operator	presubmit	Presubmit changed
pull-ci-quay-quay-operator-master-ocp-latest-ci-bundle-quay	quay/quay-operator	presubmit	Ci-operator config changed
pull-ci-quay-quay-operator-master-ocp-latest-e2e	quay/quay-operator	presubmit	Ci-operator config changed
pull-ci-quay-quay-operator-master-ocp-latest-e2e-upgrade	quay/quay-operator	presubmit	Ci-operator config changed
pull-ci-quay-quay-operator-master-ocp-latest-verify-deps	quay/quay-operator	presubmit	Ci-operator config 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.

[jbpratt]

/pj-rehearse ack

[openshift-merge-bot]

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

[Marcusk19]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jbpratt, Marcusk19

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:

• ci-operator/config/quay/quay-operator/OWNERS [Marcusk19,jbpratt]
• ci-operator/jobs/quay/quay-operator/OWNERS [Marcusk19,jbpratt]

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

[openshift-ci]

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