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.

Sign up for GitHub

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

Jump to bottom

Migrate away from google.com gcp project kubernetes-node-e2e-images #1527

Open
spiffxp opened this issue Jan 13, 2021 · 35 comments
Open

Migrate away from google.com gcp project kubernetes-node-e2e-images #1527

spiffxp opened this issue Jan 13, 2021 · 35 comments
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
sig-k8s-infra sig-testing issues

Comments

@spiffxp
Copy link
Member

spiffxp commented Jan 13, 2021

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

Part of umbrella to migrate kubernetes e2e test images/registries to community-owned infrastructure: #1458

This project is referenced in kubernetes/kubernetes as a default project (ref: https://cs.k8s.io/?q=kubernetes-node-e2e-images&i=nope&files=&repos=)

However, it may not actually be in use?

$ gcloud container images list --repository=gcr.io/kubernetes-node-e2e-images
Listed 0 items.
$ gsutil ls -p kubernetes-node-e2e-images
$

This covers:

  • determining if the project is used for anything
  • if so, identify whether an existing or new CNCF-owned gcp project should be used instead
  • it not, remove references to this project

/wg k8s-infra
/sig testing
/sig release
/area release-eng
/sig node
@k8s-ci-robot k8s-ci-robot added wg/k8s-infra sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject sig/node Categorizes an issue or PR as relevant to SIG Node. labels Jan 13, 2021
@spiffxp spiffxp mentioned this issue Jan 13, 2021
Open
55 tasks
@spiffxp spiffxp added this to Backlog in sig-k8s-infra Jan 20, 2021
@spiffxp spiffxp moved this from Backlog to Backlog (infra to migrate) in sig-k8s-infra Jan 20, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jan 21, 2021

/milestone v1.21

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Jan 21, 2021
@spiffxp spiffxp mentioned this issue Jan 21, 2021
Open
7 tasks
@spiffxp spiffxp added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jan 22, 2021
@spiffxp spiffxp added this to To Triage in sig-testing issues Feb 9, 2021
@BobyMCbobs
Copy link
Member

According to https://cs.k8s.io/?q=kubernetes-node-e2e-images&i=nope&files=&excludeFiles=&repos=, it appears that this project may not have been used since around 2016.

@ameukam
Copy link
Member

ameukam commented Apr 15, 2021

/milestone v1.22

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.21, v1.22 Apr 15, 2021
@ameukam
Copy link
Member

ameukam commented Jun 4, 2021

@spiffxp This project may be used for compute images. Can you check :

gcloud compute images list --project="kubernetes-node-e2e-images" | grep "e2e-node"

@spiffxp spiffxp moved this from To Triage to Backlog in sig-testing issues Jul 27, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jul 27, 2021 •
edited
Loading

@ameukam There are very much some images here, and I see it listed in docs and as a default, but I can't tell that it's actually what is used for node-e2e tests. These all seem pretty old to me.

$ gcloud compute images list --project="kubernetes-node-e2e-images" | grep "e2e-node"
e2e-node-containervm-v20160321-image                  kubernetes-node-e2e-images                                                READY
e2e-node-containervm-v20160604-image                  kubernetes-node-e2e-images                                                READY
e2e-node-containervm-v20161208-image                  kubernetes-node-e2e-images                                                READY
e2e-node-coreos-alpha-1068-20160707-image             kubernetes-node-e2e-images                                                READY
e2e-node-coreos-stable20160218-image                  kubernetes-node-e2e-images                                                READY
e2e-node-coreos-stable20160531-image                  kubernetes-node-e2e-images                                                READY
e2e-node-coreos-stable20160622-image                  kubernetes-node-e2e-images                                                READY
e2e-node-ubuntu-trusty-docker10-image                 kubernetes-node-e2e-images                                                READY
e2e-node-ubuntu-trusty-docker10-v1-image              kubernetes-node-e2e-images                                                READY
e2e-node-ubuntu-trusty-docker10-v2-image              kubernetes-node-e2e-images                                                READY
e2e-node-ubuntu-trusty-docker12-v1-image              kubernetes-node-e2e-images                                                READY
e2e-node-ubuntu-trusty-docker12-v2-image              kubernetes-node-e2e-images                                                READY
e2e-node-ubuntu-trusty-docker8-image                  kubernetes-node-e2e-images                                                READY
e2e-node-ubuntu-trusty-docker9-image                  kubernetes-node-e2e-images                                                READY
e2e-node-ubuntu-trusty-docker9-v1-image               kubernetes-node-e2e-images                                                READY

@spiffxp
Copy link
Member Author

spiffxp commented Jul 27, 2021

/remove-priority important-soon
/priority important-longterm
/milestone v1.23
I don't see this eating a lot of project resources but that makes it even lower hanging fruit to remove. Let's get references to this out of source once the release cycle opens back up

@k8s-ci-robot k8s-ci-robot added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jul 27, 2021
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.22, v1.23 Jul 27, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Sep 2, 2021

/remove-priority important-longterm
/priority important-soon

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 2, 2021
@endocrimes
Copy link
Member

/cc

@k8s-ci-robot k8s-ci-robot added the sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. label Sep 29, 2021
@k8s-ci-robot
Copy link
Contributor

@endocrimes: Reopened this issue.

In response to this:

/reopen

I think we just need Google infra folks to remove the project now?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot reopened this Jun 3, 2022
sig-k8s-infra automation moved this from Done to Needs Triage Jun 3, 2022
sig-testing issues automation moved this from Done to Backlog Jun 3, 2022
@endocrimes endocrimes moved this from Needs Triage to Done in sig-k8s-infra Jun 3, 2022
@endocrimes endocrimes moved this from Done to In Progress in sig-k8s-infra Jun 3, 2022
@endocrimes endocrimes moved this from Backlog to In Progress in sig-testing issues Jun 3, 2022
@BenTheElder
Copy link
Member

I do appear to have access to project owner from this one via a group, but I'm extra hesistant to delete projects I'm not involved with directly.

I think my preference would be to soft disable first, but it looks like we've already deleted all VM images in the project?

@ameukam
Copy link
Member

ameukam commented Jun 8, 2022

I think my preference would be to soft disable first, but it looks like we've already deleted all VM images in the project?

The VM images are now unused since we migrate the tests to the public GCP compute images. I'll suggest to disable to the Compute Engine API if we are hesitant to delete this project.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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:

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

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

/close

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active 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:

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

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

sig-k8s-infra automation moved this from In Progress to Done Jul 8, 2022
sig-testing issues automation moved this from In Progress to Done Jul 8, 2022
@endocrimes
Copy link
Member

/reopen
/lifecycle frozen

I think @BenTheElder is on PTO, but hopefully we can finish this when he's back

@k8s-ci-robot k8s-ci-robot reopened this Jul 8, 2022
@k8s-ci-robot
Copy link
Contributor

@endocrimes: Reopened this issue.

In response to this:

/reopen
/lifecycle frozen

I think @BenTheElder is on PTO, but hopefully we can finish this when he's back

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

sig-k8s-infra automation moved this from Done to Needs Triage Jul 8, 2022
sig-testing issues automation moved this from Done to Backlog Jul 8, 2022
@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jul 8, 2022
@endocrimes
Copy link
Member

/assign @BenTheElder

@ameukam
Copy link
Member

ameukam commented Aug 19, 2022

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.25 milestone Aug 19, 2022
@BenTheElder
Copy link
Member

I don't have (IAM) permission to do anything to this project.
/assign @spiffxp

@BenTheElder BenTheElder removed their assignment Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
registry.k8s.io (SIG K8S Infra)
Status: No status
sig-k8s-infra
  
Needs Triage
sig-testing issues
  
Backlog
Milestone
No milestone
Development

No branches or pull requests
9 participants
@spiffxp @BenTheElder @endocrimes @ameukam @ehashman @BobyMCbobs @SergeyKanzhelev @k8s-ci-robot @k8s-triage-robot