k8s.io icon indicating copy to clipboard operation
k8s.io copied to clipboard

Migrate away from google.com gcp project gke-release

Open spiffxp opened this issue 4 years ago • 39 comments

Part of umbrella issue to migrate away from google.com gcp projects: https://github.com/kubernetes/k8s.io/issues/1469

Part of umbrella to migrate kubernetes e2e test images/registries to community-owned infrastructure: https://github.com/kubernetes/k8s.io/issues/1458

There are a variety of gcr.io/gke-release images referenced in kubernetes/kubernetes CI (and sundry kubernetes-sigs projects). These should be migrated to k8s.gcr.io where possible.

Suggested path forward:

  • Gather the list of images from cs.k8s.io: https://cs.k8s.io/?q=gcr.io%2Fgke-release&i=nope&files=&repos=
  • For each image
    • determine whether there is an equivalent in k8s.gcr.io
    • if not, work with subproject owner to setup a staging project if they need one; build / stage / promote to k8s.gcr.io
    • change reference to images to k8s.gcr.io
  • announce deprecation window
  • flag project for deletion post-deprecation window

/wg k8s-infra /area artifacts /sig testing /sig release /sig storage (I see a number of csi images) /sig windows (I see a pause-win image) /area release-eng

spiffxp avatar Jan 13 '21 19:01 spiffxp

/milestone v1.21

spiffxp avatar Jan 21 '21 18:01 spiffxp

We've already added Windows support to the pause image, and it has already been built and promoted. Here's a PR that will replace the windows pause image references: https://github.com/kubernetes/kubernetes/pull/98205

claudiubelu avatar Jan 26 '21 18:01 claudiubelu

@spiffxp I can help here will assign to myself to start the work

/assign

cpanato avatar Jan 26 '21 18:01 cpanato

Some questions:

The following images do not exist in the community registry and it is defined in this file but the tags do not exist on those files

  • gcr.io/gke-release/nvidia-gpu-device-plugin@sha256:a75ec0caa9e3038bd9886b3f36641a624574ff34b064974de6ee45048de3372b
  • gcr.io/gke-release/gcp-compute-persistent-disk-csi-driver:v1.0.1-gke.0

Will be easier we just copy those images to the community registry? or where this is defined so we can set up the appropriate jobs to build those images and push them to the correct place.


And the final one is related to some go files

those files: https://github.com/kubernetes/kubernetes/blob/master/test/utils/image/manifest_test.go and https://github.com/kubernetes/kubernetes/blob/master/test/utils/image/manifest.go define the gcr.io/gke-release what should be the replacement for that?

cc @spiffxp if you can help me on that or point who can help

mentioning @LappleApple for visibility and maybe for future support.

cpanato avatar Feb 05 '21 12:02 cpanato

/milestone v1.22

spiffxp avatar Apr 15 '21 21:04 spiffxp

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

fejta-bot avatar Jul 14 '21 22:07 fejta-bot

/remove-lifecycle stale Not yet sure what the state of this is

spiffxp avatar Jul 15 '21 02:07 spiffxp

I will get back to this, it is missing one image, that I need to follow up

cpanato avatar Jul 15 '21 07:07 cpanato

Updated the PR https://github.com/kubernetes/kubernetes/pull/100294 and after we merge that we can close this issue

cpanato avatar Jul 15 '21 14:07 cpanato

found two more, the others are in the vendors directory or is a legacy that we will not change

cpanato avatar Jul 16 '21 07:07 cpanato

/milestone v1.23 We're real real close, I'll check out cs.k8s.io at some point in the next week

spiffxp avatar Jul 27 '21 04:07 spiffxp

https://cs.k8s.io/?q=gcr.io%2Fgke-release&i=nope&files=&excludeFiles=vendor%2F&repos=

Repos that still reference gcr.io/gke-release:

  • [x] kubernetes-sigs/gcp-compute-persistent-disk-csi-driver (https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/pull/836)
  • [ ] kubernetes-sigs/gcp-filestore-csi-driver (https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/pull/174)
  • [x] kubernetes/cloud-provider-gcp (https://github.com/kubernetes/cloud-provider-gcp/pull/249)

spiffxp avatar Sep 02 '21 19:09 spiffxp

will work on those

cpanato avatar Sep 03 '21 09:09 cpanato

PR for kubernetes-sigs/gcp-compute-persistent-disk-csi-driver: https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/pull/836

PR for kubernetes-sigs/gcp-filestore-csi-driver: https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/pull/174

cpanato avatar Sep 03 '21 09:09 cpanato

@spiffxp I dont see anything left for cloud-provider-gcp repo https://cs.k8s.io/?q=gcr.io%2Fgke-release&i=nope&files=&excludeFiles=vendor%2F&repos=kubernetes/cloud-provider-gcp

am I missing something?

cpanato avatar Sep 03 '21 09:09 cpanato

am I missing something?

https://github.com/kubernetes/cloud-provider-gcp/pull/249 merged which took care of that repo

spiffxp avatar Sep 03 '21 11:09 spiffxp

We're waiting on https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/pull/174 before we can call this done

spiffxp avatar Sep 29 '21 19:09 spiffxp

/milestone v1.24

spiffxp avatar Nov 24 '21 00:11 spiffxp

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

k8s-triage-robot avatar Feb 22 '22 00:02 k8s-triage-robot

/remove-lifecycle stale

ameukam avatar Feb 22 '22 09:02 ameukam

/milestone v1.25

ameukam avatar May 04 '22 11:05 ameukam

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

k8s-triage-robot avatar Aug 02 '22 12:08 k8s-triage-robot

/remove-lifecycle stale /milestone v1.26

ameukam avatar Aug 19 '22 21:08 ameukam

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

k8s-triage-robot avatar Nov 17 '22 22:11 k8s-triage-robot

/remove-lifecycle stale /milestone v1.27

ameukam avatar Nov 18 '22 11:11 ameukam

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

k8s-triage-robot avatar Feb 16 '23 11:02 k8s-triage-robot

/remove-lifecycle stale

cpanato avatar Feb 16 '23 11:02 cpanato

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

k8s-triage-robot avatar May 17 '23 11:05 k8s-triage-robot

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Jun 16 '23 12:06 k8s-triage-robot

/remove-lifecycle stale

riaankleinhans avatar Jun 19 '23 07:06 riaankleinhans