Add inputs for cincinnati-operator Dockerfile builder stage

[deepsm007]

https://redhat-internal.slack.com/archives/CBN38N3MW/p1781013922005829

After ART migrated builder imagestreams to push directly to QCI instead of registry.ci.openshift.org (art-tools#3025), the cincinnati-operator Dockerfile still pulls registry.ci.openshift.org/ocp/builder directly and fails with manifest unknown.

Add inputs mapping that FROM to pipeline:root (already imported from quay-proxy via build_root) so the image build no longer depends on the removed registry.ci tag.

/cc @openshift/test-platform

Summary by CodeRabbit

This PR updates the OpenShift CI configuration for the openshift/cincinnati-operator repository to fix a broken image build. The cincinnati-operator's image build (build/Dockerfile) referenced the now-removed registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.18 tag and failed with "manifest unknown". The change adds an inputs mapping for the image build's root input so the Dockerfile's FROM that previously pointed at the registry.ci builder tag is provided from the pipeline image (pipeline:root), which is already imported via the existing build_root configuration. As a result, the image build will pull from quay-proxy/pipeline:root instead of the deleted registry.ci tag, avoiding manifest errors without modifying the repository's Dockerfile or source code.

[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: 0b4a6c94-0bbf-44d6-a34c-d684f845ab47

📥 Commits

Reviewing files that changed from the base of the PR and between 3e4932c and e247d4b.

📒 Files selected for processing (1)

• ci-operator/config/openshift/cincinnati-operator/openshift-cincinnati-operator-master.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

• ci-operator/config/openshift/cincinnati-operator/openshift-cincinnati-operator-master.yaml

---

Walkthrough

The Cincinnati Operator CI config adds an inputs.root.as override for the build/Dockerfile image, specifying the RHEL 9 Go 1.22 OpenShift builder image registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.18.

Changes

Cincinnati Operator builder image configuration

Layer / File(s)	Summary
Cincinnati Operator builder image configuration ci-operator/config/openshift/cincinnati-operator/openshift-cincinnati-operator-master.yaml	Build-root input mapping updated to include the OpenShift RHEL 9 Go 1.22 builder image reference (registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.18).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 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 accurately describes the main change: adding inputs for the cincinnati-operator Dockerfile builder stage to resolve a builder imagestream migration issue.
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 modifies only YAML CI configuration file, not Ginkgo test code; check is not applicable to this PR type.
Test Structure And Quality	✅ Passed	PR only modifies CI configuration YAML file; no Ginkgo test code present. Custom check for test structure/quality is not applicable to infrastructure configuration changes.
Microshift Test Compatibility	✅ Passed	PR modifies only CI config YAML file, not test code. No Ginkgo e2e tests added; check for test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR adds no new Ginkgo e2e tests. It only modifies a CI operator YAML configuration file for the cincinnati-operator builder stage. Check applies only to PRs adding Ginkgo tests.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies a CI build configuration file with no deployment manifests, scheduling constraints, pod affinity, topology spread, or related topology-aware configurations.
Ote Binary Stdout Contract	✅ Passed	PR modifies only YAML CI configuration files with no executable code that could violate stdout contract; check not applicable to configuration-only changes.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only a CI config YAML file, not adding any new Ginkgo e2e tests. The check does not apply to CI configuration changes.
No-Weak-Crypto	✅ Passed	PR modifies only CI/CD YAML config (builder image mapping), no source code. No weak crypto, custom implementations, or secret comparisons present.
Container-Privileges	✅ Passed	The PR modifies a CI-operator build configuration file, not a K8s/container manifest. No privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings are present.
No-Sensitive-Data-In-Logs	✅ Passed	No sensitive data like passwords, tokens, API keys, or PII exposed. Registry URL and credential infrastructure references are standard boilerplate, not actual secrets.

_{✏️ 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-merge-bot]

@coderabbitai[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.

[openshift-merge-bot]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@deepsm007: 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-cincinnati-operator-master-ci-bundle-cincinnati-bundle	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-fips-image-scan-operator	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-gofmt	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-images	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-install-bundle	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-install-bundle-tls-scan	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-operator-e2e-hypershift-local-graph-data	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-operator-e2e-new-ocp-published-graph-data	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-operator-e2e-new-ocp-published-graph-data-fips	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-operator-e2e-old-ocp-published-graph-data	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-scorecard	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-unit	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-verify-crypto	openshift/cincinnati-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cincinnati-operator-master-verify-generate	openshift/cincinnati-operator	presubmit	Ci-operator config changed
periodic-ci-openshift-cincinnati-operator-master-fips-image-scan-operator-production	N/A	periodic	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.

[deepsm007]

/pj-rehearse pull-ci-openshift-cincinnati-operator-master-images

[openshift-merge-bot]

@deepsm007: 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]: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

[openshift-merge-bot]

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

[openshift-merge-bot]

@deepsm007: pj-rehearse could not automatically process this event because the request waited in queue for longer than 5 minutes. Use /pj-rehearse to trigger rehearsals manually.

[openshift-merge-bot]

@openshift-merge-bot[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.

[openshift-ci]

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

[danilo-gemoli]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danilo-gemoli, deepsm007

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/openshift/cincinnati-operator/OWNERS [danilo-gemoli,deepsm007]

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]

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

[deepsm007]

/hold

[deepsm007]

/close in favor of openshift/ci-tools#5244