Skip to content

core-services/prow/README: Talk about Boskos capacity #10303

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.

Sign up for GitHub

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

Closed
wking wants to merge 1 commit into from
Closed

core-services/prow/README: Talk about Boskos capacity #10303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions core-services/prow/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,14 @@

Manifests and configuration of the OpenShift instance of [Prow](https://github.com/kubernetes/test-infra/blob/master/prow/README.md)
running on the api.ci cluster.

## Boskos

The CI clusters provide a [Boskos][] service which manages platform-specific leases to avoid failing jobs based on available capacity (e.g. VPC limits or throttling on AWS).
Per-platform administrators [configure lease capacity][boskos-lease-config] to reflect the currently-available capacity for each account.
Cluster-launching jobs acquire leases before launching a cluster, and release them after tearing the cluster back down.
When capacity is exhausted, jobs may wait some time before a lease becomes available.
If no leases become available, the job may fail on a lease timeout.

[Boskos]: https://github.com/kubernetes-sigs/boskos#boskos
[boskos-lease-config]: 02_config/_boskos.yaml