-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prow-scheduler: Enable scheduling #49983
prow-scheduler: Enable scheduling #49983
Conversation
[REHEARSALNOTIFIER] |
If it is going to work, this PR formally concludes: Scheduling in Prow |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danilo-gemoli, jmguzik 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:
Approvers can indicate their approval by writing |
@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: Updated the
In response to this:
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. |
ProwJob CRD has been updated #49766 and the scheduler is actually running #49859.
This PR enables a PJ to be created in
state: scheduling
by the components cited in these PRs:The current scheduling strategy is
failover
with no mappings (see here), so this means the scheduler will simply update.status.state
of each PJ, leaving.spec.cluster
untouched.The following is an example of how the reconciler would patch a PJ:
/cc @openshift/test-platform