Dynamic scheduling of Prowjobs to clusters

[danilo-gemoli]

What would you like to be added:
I want to introduce a scheduler that dynamically dispatches ProwJobs across clusters.

Why is this needed:
Increase fault tolerance, reduce operation burden and CI costs.

Design doc here.

/cc @petr-muller @stevekuznetsov @droslean @smg247 @jmguzik

[danilo-gemoli]

/sig testing
/label area/prow

[k8s-ci-robot]

@danilo-gemoli: The label(s) /label area/prow cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/sig testing
/label area/prow

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.

[petr-muller]

/area prow

[petr-muller]

/retitle Dynamic scheduling of Prowjobs to clusters

[stevekuznetsov]

I like the proposal and think the backwards-compatible and incremental process proposed is a great way forward/

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale