Migrate away from google.com GCP project google-containers

[spiffxp]

Part of umbrella issue to migrate away from google.com gcp projects: #1469

This GCP project has historically hosted the kubernetes project's artifacts in GCR and GCS.

Suggested path forward:

• migrate away from gcr.io/google-containers
  • use k8s.gcr.io instead of gcr.io/google-containers (k8s.gcr.io VDF (Vanity Domain Flip): Move official container images to K8s Infra release#270)
  • ensure artifact promotion is fully supported by sig-release ([Umbrella Issue] Create a Image Promotion process #157 (comment))
• deprecate and migrate away from gs://kubernetes-release-dev and gcr.io/kubernetes-ci-images (Deprecate and migrate away from gs://kubernetes-release-dev and gcr.io/kubernetes-ci-images #2318)
• depercate and migrate away from gs://kubernetes-release - binaries (e.g. tar.gz artifacts listed in kubernetes/kubernetes CHANGELOG) - Deprecate and migrate away from gs://kubernetes-release #2396
• identify any remaining service accounts / IAM permissions that the project uses

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

/milestone v1.21
I doubt we'll have this completely addressed within v1.21, but I'd like to see us make progress on some of the individual pieces.

[spiffxp]

/priority important-longterm

[spiffxp]

/milestone v1.23

[spiffxp]

Here's traffic in terms of bytes sent for the artifacts that are currently community-hosted (k8s.gcr.io, gs://k8s-artifacts-prod). This exclude staging projects.

Here's traffic in terms of bytes sent for gs://kubernetes-release (and its regional buckets), which has yet to be migrated

[ameukam]

/milestone v1.24

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ameukam]

/remove-lifecycle stale

[ameukam]

/milestone v1.30
/remove-lifecycle stale

[ameukam]

/milestone v1.31

[BenTheElder]

We're still just pending gs://kubernetes-release, I've been talking to @ameukam about plans for this but they haven't shipped yet. The Fastly CDN is in place in front of it.

I recently worked with some googlers internally to spin down GKE clusters in this project.

[BenTheElder]

On the google side: further restricted access to this but left a temporary carve-out to keep publishing releases until #2396 is resolved

[ameukam]

/milestone v1.32

[k8s-triage-robot]

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

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ameukam]

/remove-lifecycle stale

[BenTheElder]

I need to update the permissions but this is otherwise ~done now. I will look later.

[BenTheElder]

Sent cl/707294470 internally to drop remaining Kubernetes project service account access and make what's left here ~read-only.

[BenTheElder]

kubernetes/release#3425 is not this project, but related.

Otherwise this is ~done. Downstream users will still take time to migrate (... like cncf/k8s-conformance#3512) but over time as they desire currently releases they'll naturally move to dl.k8s.io (and already had to for some time for registry.k8s.io).