Closed
Description
Currently, the Kubernetes community prow instance (prow.k8s.io) is supporting a number of non-Kubernetes project repositories. We need to migrate these off the Kubernetes community infrastructure ahead of moving our instance onto project owned infrastructure.
We should also stop adding any new repos/orgs to the prow.k8s.io instance that aren't directly involved with the Kubernetes project.
Currently, I see the following repos/orgs with configuration in config.yaml/plugins.yaml:
- https://github.com/bazelbuild/rules_k8s (Remove lingering prow config for non-Kubernetes repos #32089)
- https://github.com/client-go/unofficial-docs (Don't use prow for client-go/unofficial-docs #12870)
- https://github.com/google/cadvisor
- https://github.com/kubeflow (ref: Move kubeflow jobs to https://github.com/GoogleCloudPlatform/oss-test-infra/tree/master/prow/prowjobs #14343)
- https://github.com/helm/charts (ref: Removing helm/charts from test-infra #19946)
-
https://github.com/containerd/crihttps://github.com/containerd/containerd - https://github.com/tensorflow/k8s (remove tensorflow/minigo from config as it is archived #21591)
- https://github.com/tensorflow/minigo (remove tensorflow/minigo from config as it is archived #21591)
- https://github.com/spxtr/envoy (remove spxtr/envoy from config #18297)
- https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress (remove kubemci jobs that are failing permanently #26297)
- https://github.com/GoogleCloudPlatform/k8s-cluster-bundle (Remove lingering prow config for non-Kubernetes repos #32089)
- https://github.com/GoogleCloudPlatform/netd (Remove GoogleCloudPlatform/netd from Kubernetes's Prow #26324)
- https://github.com/cncf/apisnoop (REQUEST: Migrate cncf/apisnoop org#4705)
- https://github.com/cncf/k8s-conformance (remove cncf/k8s-conformance from plugins #18901)
- https://github.com/apache-spark-on-k8s/spark-integration (delete jobs for github.com/apache-spark-on-k8s/spark-integration #21141)
cc: @kubernetes/k8s-infra-team @kubernetes/sig-testing @fejta @cjwagner @Katharine @krzyzacy @amwat @michelle192837
Metadata
Metadata
Assignees
Labels
Categorizes issue or PR as related to cleaning up code, process, or technical debt.Indicates that an issue or PR should not be auto-closed due to staleness.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.Categorizes an issue or PR as relevant to SIG K8s Infra.Categorizes an issue or PR as relevant to SIG Testing.
Type
Projects
Status
Done
Status
Done