Skip to content
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.

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

Migrate non-Kubernetes repos off of prow.k8s.io #12863

Open
cblecker opened this issue Jun 4, 2019 · 7 comments

Comments

Projects
None yet
3 participants
@cblecker
Copy link
Member

commented Jun 4, 2019

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:

  • bazelbuild
  • bazelbuild/bazel-toolchains
  • bazelbuild/rules_docker
  • bazelbuild/rules_k8s
  • client-go/unofficial-docs
  • cncf/apisnoop
  • containerd/cri
  • google/cadvisor
  • GoogleCloudPlatform/k8s-cluster-bundle
  • GoogleCloudPlatform/k8s-multicluster-ingress
  • GoogleCloudPlatform/netd
  • helm/charts
  • kubeflow
  • spxtr/envoy
  • tensorflow/k8s
  • tensorflow/minigo

cc: @kubernetes/k8s-infra-team @kubernetes/sig-testing @fejta @cjwagner @Katharine @krzyzacy @amwat @michelle192837

@cblecker

This comment has been minimized.

Copy link
Member Author

commented Jun 4, 2019

cc @nikhita for client-go/unofficial-docs

@cblecker

This comment has been minimized.

Copy link
Member Author

commented Jun 4, 2019

cc @Random-Liu for containerd/cri

@nikhita

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

cc @nikhita for client-go/unofficial-docs

This is not active and can be removed even right now. 👍

@krzyzacy

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

For google owned projects' owners: feel free to migrate to https://github.com/GoogleCloudPlatform/oss-test-infra instead

@cblecker

This comment has been minimized.

Copy link
Member Author

commented Jun 4, 2019

@krzyzacy Do we have owners/contacts for the google owned projects?

@krzyzacy

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

@cblecker you can check 😂 I think it can fall back to us, or maybe @spiffxp can also help coordinate?

@cblecker

This comment has been minimized.

Copy link
Member Author

commented Jun 4, 2019

Looking at the configs, we probably don't need to worry about cncf/apisnoop (CNCF project and only using meow/bark).

We also may want to keep helm/charts around as it is also a CNCF project and may provide valuable signal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.