search

kubernetes / k8s.io

Code and configuration to manage Kubernetes project infrastructure, including various *.k8s.io sites
https://git.k8s.io/community/sig-k8s-infra
Apache License 2.0
730 stars 807 forks source link

Umbrella issue: migrate away from google.com gcp projects #1469

Open spiffxp opened 3 years ago

spiffxp commented 3 years ago

An umbrella issue for wg-k8s-infra's mission: migrate project infrastructure away from the google.com GCP org, to the CNCF-owned/community-managed kubernetes.io GCP org.

Projects that host infrastructure (services, images, gcs buckets, service accounts, clusters, etc)

Projects referenced by kubernetes/kubernetes CI (roughly https://github.com/kubernetes/k8s.io/issues/1469)

Projects that host release or CI artifacts

Projects that are used for e2e testing (pinned to via --gcp-project=foo)

Projects that are used for e2e testing (those managed by prow.k8s.io's "default" cluster's boskos)

Other projects used directly by kubernetes subprojects

/wg k8s-infra /sig testing /sig release /area release-eng

riaankleinhans commented 3 years ago

Migrate away from google.com GCP project google-containers #1571 is related to this issue, but not hyperlinked in the description. Adding this comment just to help to track related issues.

ameukam commented 3 years ago

I found a bunch of GCP buckets that can potentially need be migrated:

I couldn't find how they were created and which group(s) have admin access to them.

spiffxp commented 3 years ago

gs://kops-ci

I don't have access to this, @justinsb ?

gs://cloud-sdk-testing

This lives someplace google-internal and can't be moved. Honestly, I question whether jobs that use this should be public.

gs://k8s-testimages-scratch

This lives in k8s-testimages. If we're moving gcr.io/k8s-testimages to gcr.io/k8s-staging-test-infra/images, we should use gs://k8s-staging-test-infra-scratch

gs://sig-scalability-logs

This lives in kubernetes-jenkins. I would be fine with us rsyncing to gs://k8s-infra-scalability-test-logs if we've moved the old jobs (vs. waiting for it to age out)

gs://kubernetes-e2e-soak-configs

This lives in kubernetes-jenkins. I question the value of these soak jobs since they are perma-failing. We can create equivalent buckets in kubernetes-public if there is interest from a SIG in staffing ownership of these jobs

gs://cri-containerd-staging

This lives in k8s-cri-containerd. These jobs should be changed to use a k8s-staging project and promotion workflow. We'll need SIG Node to take this on.

spiffxp commented 3 years ago

/milestone v1.23

BenTheElder commented 3 years ago

Also not sure k8s should be staging cri-containerd at all?

BenTheElder commented 3 years ago

https://github.com/kubernetes/k8s.io/issues/1311 is done.

leilajal commented 3 years ago

hey we just realized kubebuildr uses a google-internal project

ameukam commented 2 years ago

/milestone v1.24

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

ameukam commented 2 years ago

/remove-lifecycle stale

ameukam commented 2 years ago

/milestone v1.25

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

spiffxp commented 2 years ago

/remove-lifecycle stale /lifecycle frozen

ameukam commented 2 years ago

/milestone v1.26 I'll try to do a few things before EOY.

ameukam commented 1 year ago

/milestone v1.27