Showing content from https://github.com/kubernetes/k8s.io/issues/752 below:
Develop a prow migration plan · Issue #752 · kubernetes/k8s.io · GitHub
Break out into issues when we've gotten consensus
Current sketch is:
- decide whether we want a build cluster, and/or how many we we want
- allow prow.k8s.io to schedule jobs on our build cluster(s)
- setup a prow instance (in aaa?)
- figure out how we want to migrate/cut-over github traffic
Some concerns include:
- jobs that run in same cluster as prow.k8s.io to take advantage of the ghproxy instance that lives there
- using a new github bot user/token so as not to conflict with k8s-ci-robot while prow.k8s.io continues to use it
- setting up boskos in our build cluster(s)
- setting up greenhouse in our build cluster(s)
- setting up projects for boskos to manage
- migration of google-owned buckets like kubernetes-jenkins
- on-call
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4