Migrate non-kubernetes orgs and repos off of prow.k8s.io

[spiffxp]

What should be cleaned up or changed:
We should stop accepting k8s-adjacent projects, and make prow.k8s.io an instance of prow responsible solely for the kubernetes project.

Migrate non-kubernetes orgs and repos off of prow.k8s.io

Specifically:

• https://github.com/bazelbuild
• https://github.com/google/cadvisor
• https://github.com/kubeflow
• https://github.com/helm/charts
• https://github.com/containerd/cri
• https://github.com/tensorflow/k8s
• https://github.com/tensorflow/minigo
• https://github.com/spxtr/envoy
• https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress
• https://github.com/GoogleCloudPlatform/k8s-cluster-bundle
• https://github.com/GoogleCloudPlatform/netd
• https://github.com/cncf/apisnoop
• https://github.com/cncf/k8s-conformance

There's also the option of asking the maintainers of these projects to donate them to Kubernetes if a SIG is willing to take ownership (ref: https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#rules-for-donated-repositories)

Provide any links for context:

[clarketm]

For each project we choose to migrate: a proposal to minimize risk of downtime is:

• Phase 1: migrating project to a dedicated build cluster (e.g. Kubeflow Prow Migration)
• Phase 2: setup bot, webhooks, transfigure, and port Prow config, plugins, kubeconfig and jobs to new instance (ideally with support from tools offered by Prow).
• Phase 3: miscellaneous cleanup task: delete artifacts, redefine cluster, rerun, and bot permissions, and copy over historical job results.

Caveat: the above may not be comprehensive but it is what I have gathered from my experience with Prow migration thus far. Please provide input here or in doc.

[spiffxp]

/close
closing in favor of #12863

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close
closing in favor of #12863

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.