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

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

Open
36 of 55 tasks
spiffxp opened this issue Dec 8, 2020 · 15 comments
Open
36 of 55 tasks

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

spiffxp opened this issue Dec 8, 2020 · 15 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. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@spiffxp
Copy link
Member

spiffxp commented Dec 8, 2020 •
edited by ameukam
Loading

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 #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
@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 labels Dec 8, 2020
This was referenced Dec 8, 2020
Closed
Closed
Closed
Closed
Open
Closed
Closed
This was referenced Jan 13, 2021
Open
Closed
Open
Open
Open
Closed
Closed
This was referenced Jan 21, 2021
Open
Open
@spiffxp spiffxp added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jan 22, 2021
@spiffxp spiffxp mentioned this issue Jan 29, 2021
Merged
@spiffxp spiffxp mentioned this issue Feb 8, 2021
Closed
@riaankleinhans riaankleinhans mentioned this issue Mar 22, 2021
Closed
@riaankleinhans
Copy link
Contributor

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 ameukam added this to the v1.22 milestone May 7, 2021
ameukam added a commit to ameukam/test-infra that referenced this issue May 13, 2021
@ameukam
Add a canary job for ci-kubernetes-kubemark-gce-scale
4eae01b 
Ref: kubernetes/k8s.io#1469

Add a canary job to ensure ci-kubernetes-kubermark-gce-scale can run on
the community build clusters and use boskos project type
`scalability-project`.

Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
@ameukam ameukam mentioned this issue May 13, 2021
Closed
@ameukam
Copy link
Member

ameukam commented Dec 6, 2021

/milestone v1.24

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.23, v1.24 Dec 6, 2021
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 6, 2022
@ameukam
Copy link
Member

ameukam commented Apr 6, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 6, 2022
@ameukam
Copy link
Member

ameukam commented May 12, 2022

/milestone v1.25

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.24, v1.25 May 12, 2022
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 10, 2022
@spiffxp
Copy link
Member Author

spiffxp commented Aug 19, 2022

/remove-lifecycle stale
/lifecycle frozen

@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/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 19, 2022
@ameukam
Copy link
Member

ameukam commented Aug 19, 2022

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

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.25, v1.26 Aug 19, 2022
@riaankleinhans riaankleinhans moved this to Migrate away issues in registry.k8s.io (SIG K8S Infra) Jan 4, 2023
@ameukam
Copy link
Member

ameukam commented Jan 19, 2023

/milestone v1.27

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.26, v1.27 Jan 19, 2023
@ameukam ameukam moved this to In Progress in SIG K8S Infra Feb 4, 2023
@ameukam ameukam removed the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Feb 22, 2023
@ameukam ameukam removed this from the v1.27 milestone Feb 22, 2023
This was referenced Jun 30, 2023
Merged
Merged
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. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. 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
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
7 participants
@spiffxp @BenTheElder @ameukam @k8s-ci-robot @k8s-triage-robot @riaankleinhans @leilajal