prow-scheduler: Add scheduler in prow-controller-manager

[danilo-gemoli]

Add the scheduler in prow-controller-manager.
The flag --enable-controller=plank is also needed since plank is enabled by default only when no controller is passed as an argument.
This PR doesn't enable scheduling because it doesn't set:

scheduler:
  enabled: true

therefore ProwJobs are still being created in triggered state by each component in Prow.

I just want to make sure the scheduler controller runs and doesn't cause any trouble at least.
I will watch the rolling and, if everything goes smoothly, I am going to enable scheduling as well.

[danilo-gemoli]

time="2024-03-14T08:46:06Z" level=fatal msg="could not update Prow configuration" error="failed to load Prow config in strict mode: error unmarshaling /tmp/tmp.L3vC3R6cCc/_config.yaml: error unmarshaling JSON: while decoding JSON: json: unknown field \"scheduler\""

Ok we have some inter-repository dependencies. I can't use a new Prow configuration in o/release if Prow isn't up to date in o/ci-tools and I can't update Prow in o/ci-tools if it hasn't been updated in o/ci-chat-bot and o/release-controller too.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@danilo-gemoli: no rehearsable tests are affected by this change

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 abort to abort all active rehearsals

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.

[danilo-gemoli]

/hold
it needs openshift/ci-tools#4047

[danilo-gemoli]

/retest

[openshift-ci]

@danilo-gemoli: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[danilo-gemoli]

/unhold

[Prucek]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• clusters/app.ci/prow/OWNERS [Prucek,danilo-gemoli]
• core-services/prow/02_config/OWNERS [Prucek,danilo-gemoli]

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

[openshift-ci]

@danilo-gemoli: Updated the config configmap in namespace ci at cluster app.ci using the following files:

• key config.yaml using file core-services/prow/02_config/_config.yaml

In response to this:

Add the scheduler in prow-controller-manager.
The flag --enable-controller=plank is also needed since plank is enabled by default only when no controller is passed as an argument.
This PR doesn't enable scheduling because it doesn't set:

scheduler:
 enabled: true

therefore ProwJobs are still being created in triggered state by each component in Prow.

I just want to make sure the scheduler controller runs and doesn't cause any trouble at least.
I will watch the rolling and, if everything goes smoothly, I am going to enable scheduling as well.

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/test-infra repository.