Onboard o/origin to dockerfile-inputs

[Prucek]

Registry-replacer is getting deprecated and ci-operator will automatically detect the inputs and base_images. This PR enables the dockerfile-inputs feature for openshift/origin by removing auto-detectable base_images and inputs entries from all configs.
Needs: openshift/ci-tools#4890

[Prucek]

/hold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Prucek

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/origin/OWNERS [Prucek]

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

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@Prucek: 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-origin-release-4.20-okd-scos-e2e-aws-ovn	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.20-okd-scos-images	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-agnostic-ovn-cmd	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-csi	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-disruptive	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-etcd-certrotation	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-etcd-recovery	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-jenkins	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-cgroupsv2	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-edge-zones	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-etcd-scaling	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-fips	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-image-registry	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-kube-apiserver-rollout	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-kubevirt	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-microshift	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-microshift-serial	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-serial	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-serial-ipsec	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node-serial	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node-techpreview	openshift/origin	presubmit	Ci-operator config changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node-techpreview-serial	openshift/origin	presubmit	Ci-operator config changed

A total of 1031 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
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.

[jmguzik]

TRT is informed about potential issues?

[Prucek]

curious if it would work before the change:
/pj-rehearse pull-ci-openshift-origin-main-images
works, but as expected takes images from registry.ci.openshift.org

Trying to pull registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.17...

And we want from quay-proxy: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/30623/pull-ci-openshift-origin-main-images/2009559473219178496/artifacts/build-logs/hello-openshift-amd64.log

[openshift-ci-robot]

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

[openshift-ci]

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