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.

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

Migrate all presubmit jobs to use boskos #7769

Open
krzyzacy opened this issue Apr 18, 2018 · 37 comments
Open

Migrate all presubmit jobs to use boskos #7769

krzyzacy opened this issue Apr 18, 2018 · 37 comments
Labels
area/boskos Issues or PRs related to code in /boskos help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@krzyzacy
Copy link
Member

We are seeing janitor/quota issues again for newly added scalability suites, also we have the log sink issue for gce presubmit. These are all solvable by using boskos projects, and we should do so to unify our presubmit/CI environment.

/area boskos
/assign

cc @shyamjvs @BenTheElder

@k8s-ci-robot k8s-ci-robot added the area/boskos Issues or PRs related to code in /boskos label Apr 18, 2018
@BenTheElder
Copy link
Member

We should do this for all presubmits :-)

@krzyzacy
Copy link
Member Author

/shrug
#8165

@k8s-ci-robot k8s-ci-robot added the ¯\_(ツ)_/¯ ¯\\\_(ツ)_/¯ label May 30, 2018
@BenTheElder
Copy link
Member

/assign

@spiffxp
Copy link
Member

spiffxp commented Aug 23, 2018

ping

@BenTheElder
Copy link
Member

we moved the blocking ones to this at least, except scalability I think :|

@krzyzacy
Copy link
Member Author

/assign @amwat
(who is working on scalability presubmits :-) )

@spiffxp
Copy link
Member

spiffxp commented Sep 27, 2018

/milestone v1.13

@k8s-ci-robot k8s-ci-robot added this to the v1.13 milestone Sep 27, 2018
@fejta-bot
Copy link

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-testing, kubernetes/test-infra and/or fejta.
/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 Dec 26, 2018
@spiffxp
Copy link
Member

spiffxp commented Jan 3, 2019

/milestone v1.14

What remains to be done here?

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.13, v1.14 Jan 3, 2019
@krzyzacy
Copy link
Member Author

krzyzacy commented Jan 3, 2019

I think scalability presubmits are the only ones left.

@shyamjvs
Copy link
Member

shyamjvs commented Jan 3, 2019

cc @amwat @krzysied

Were looking into the scalability jobs. There should be a github issue for this somewhere.

@amwat
Copy link
Contributor

amwat commented Jan 3, 2019

@shyamjvs #9223
Most of the small scalability jobs were moved to boskos in #9567

Only the large scalability tests remain. @krzyzacy IIRC the last consensus on this one was to have a boskos pool of one project?

@krzyzacy
Copy link
Member Author

krzyzacy commented Jan 3, 2019

I didn't see the presubmit jobs... maybe it's ok they fails when there's a periodic job running?

@krzyzacy
Copy link
Member Author

krzyzacy commented Jan 8, 2019

/remove-lifecycle stale

will take a stab

@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 Jan 8, 2019
@spiffxp
Copy link
Member

spiffxp commented Feb 19, 2019

/unshrug
/kind cleanup
/sig testing

@k8s-ci-robot
Copy link
Contributor

@spiffxp: ¯\_(ツ)_/¯

In response to this:

/unshrug
/kind cleanup
/sig testing

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 added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed ¯\_(ツ)_/¯ ¯\\\_(ツ)_/¯ labels Feb 19, 2019
@MHBauer
Copy link
Contributor

MHBauer commented Jun 4, 2020

I can help, but I need some guidance.
I'm tracing through some recent PRs:
from #17349 it looks we use a different arg, gcp-project to gcp-project-type
from #17359 I wonder if I need to find an entry to slot tests under or if I need to make a new one some how.
from #17452 (comment) it looks like maybe the idea is to move the pull job into the same project-type as the ci job, which I think we have for some of these.
from kubernetes/kubernetes#89847 (comment) some thoughts are linking up in my head

I may have an idea of what to do. I'm gonna circle back later and maybe push some PRs.

@spiffxp
Copy link
Member

spiffxp commented Sep 11, 2020

/remove-lifecycle frozen

Jobs that pin to a gcp-project

config/jobs/containerd/containerd/containerd-presubmit-jobs.yaml
63:          --gcp-project=cri-c8d-pr-node-e2e

config/jobs/containerd/cri/containerd-cri-presubmit-jobs.yaml
56:          --gcp-project=cri-c8d-pr-node-e2e

config/jobs/kubernetes/generated/generated.yaml
26:      - --gcp-project=ubuntu-image-validation
64:      - --gcp-project=ubuntu-image-validation
104:      - --gcp-project=ubuntu-image-validation
142:      - --gcp-project=ubuntu-image-validation
182:      - --gcp-project=ubuntu-image-validation
220:      - --gcp-project=ubuntu-image-validation
260:      - --gcp-project=ubuntu-image-validation
298:      - --gcp-project=ubuntu-image-validation
338:      - --gcp-project=ubuntu-image-validation
376:      - --gcp-project=ubuntu-image-validation
416:      - --gcp-project=ubuntu-image-validation
454:      - --gcp-project=ubuntu-image-validation
494:      - --gcp-project=ubuntu-image-validation
532:      - --gcp-project=ubuntu-image-validation
572:      - --gcp-project=ubuntu-image-validation
610:      - --gcp-project=ubuntu-image-validation
651:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
697:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
743:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
782:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
822:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
862:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
901:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
941:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
981:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1020:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1060:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1100:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1139:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1179:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1219:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1258:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1298:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1338:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1377:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1417:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1457:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1496:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1536:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1576:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests

config/jobs/kubernetes/sig-release/release-branch-jobs/1.19.yaml
1038:        - --gcp-project=k8s-jkns-pr-gce-gpus

config/jobs/kubernetes/sig-network/sig-network-misc.yaml
81:      - --gcp-project=k8s-e2e-gce-alpha-api-access
365:      - --gcp-project=k8s-jenkins-gce-gci-ip-aliases

config/jobs/kubernetes/sig-release/release-branch-jobs/1.17.yaml
886:        - --gcp-project=k8s-jkns-pr-gce-gpus

config/jobs/kubernetes/sig-release/release-branch-jobs/1.16.yaml
736:        - --gcp-project=k8s-jkns-pr-gce-gpus
1013:        - --gcp-project=k8s-presubmit-scale

config/jobs/kubernetes/sig-network/ingress-gce-e2e.yaml
246:      - --gcp-project=k8s-ingress-e2e-scale-backup

config/jobs/kubernetes/sig-release/release-branch-jobs/1.18.yaml
1087:        - --gcp-project=k8s-jkns-pr-gce-gpus

config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-presubmits.yaml
40:        - --gcp-project=k8s-jkns-gci-autoscaling

config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-config.yaml
181:      - --gcp-project=k8s-jkns-gci-autoscaling
207:      - --gcp-project=k8s-jkns-gci-autoscaling
241:      - --gcp-project=k8s-jkns-gci-autoscaling-migs
267:      - --gcp-project=k8s-jkns-gci-autoscaling-migs

config/jobs/kubernetes/sig-scalability/sig-scalability-presubmit-jobs.yaml
98:        - --gcp-project=k8s-presubmit-scale
206:        - --gcp-project=k8s-presubmit-scale
347:        - --gcp-project=k8s-presubmit-scale

config/jobs/kubernetes/sig-scalability/sig-scalability-periodic-jobs.yaml
233:      - --gcp-project=k8s-jenkins-blocking-kubemark
290:      - --gcp-project=kubemark-scalability-testing

config/jobs/kubernetes/sig-scalability/sig-scalability-golang.yaml
70:      - --gcp-project=k8s-presubmit-scale

config/jobs/kubernetes/sig-scalability/sig-scalability-release-blocking-jobs.yaml
30:      - --gcp-project=kubernetes-scale
80:      - --gcp-project=kubernetes-scale

config/jobs/kubernetes/sig-cloud-provider/gcp/gpu/gpu-gce.yaml
77:      - --gcp-project=k8s-infra-e2e-gpu-project

config/jobs/kubernetes/sig-cloud-provider/gcp/gpu/gcp-gpu-presubmits.yaml
45:        - --gcp-project=k8s-jkns-pr-gce-gpus

config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml
888:      - --gcp-project=k8s-jkns-e2e-gce-ubelite
916:      - --gcp-project=k8s-jkns-gce-gci-soak
946:      - --gcp-project=k8s-jkns-gce-soak-1-6
976:      - --gcp-project=k8s-jkns-gci-gce-soak-1-4
1005:      - --gcp-project=k8s-jkns-gci-gce-soak-1-7
1034:      - --gcp-project=k8s-jkns-gci-gce-soak-1-6

config/jobs/kubernetes/sig-cloud-provider/gcp/gce-misc.yaml
17:      - --gcp-project=kubernetes-ha-master

config/jobs/kubernetes/sig-api-machinery/sig-api-machinery-config.yaml
108:        - --gcp-project=k8s-network-proxy-e2e

config/jobs/kubernetes/sig-node/containerd.yaml
269:      - --gcp-project=cri-containerd-node-e2e
299:      - --gcp-project=cri-containerd-node-e2e
329:      - --gcp-project=cri-containerd-node-e2e
359:      - --gcp-project=cri-containerd-node-e2e
392:      - --gcp-project=k8s-jkns-e2e-gci-gce-soak-1-4
786:      - --gcp-project=cri-containerd-node-e2e
816:      - --gcp-project=cri-containerd-node-e2e
846:      - --gcp-project=cri-containerd-node-e2e
931:      - --gcp-project=cri-containerd-node-e2e
960:      - --gcp-project=cri-containerd-node-e2e

config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml
143:        - --gcp-project=k8s-jkns-pr-node-e2e
179:            - --gcp-project=k8s-jkns-pr-node-e2e
213:            - --gcp-project=k8s-jkns-pr-node-e2e
247:            - --gcp-project=k8s-jkns-pr-node-e2e
284:        - --gcp-project=k8s-jkns-pr-node-e2e

config/jobs/cadvisor/cadvisor.yaml
40:        - --gcp-project=cadvisor-e2e
96:      - --gcp-project=ci-cadvisor-e2e

/unshrug
/sig node
A number of the jobs that still pin are sig-node jobs. I don't know if there's something special about those projects, but I know we've successfully migrated a few node e2e projects to use the standard gce-project pool boskos offers up
/sig scalability
/sig network
/sig autoscaling
based on some of the other paths

@k8s-ci-robot
Copy link
Contributor

@spiffxp: ¯\_(ツ)_/¯

In response to this:

/remove-lifecycle frozen

Jobs that pin to a gcp-project

config/jobs/containerd/containerd/containerd-presubmit-jobs.yaml
63:          --gcp-project=cri-c8d-pr-node-e2e

config/jobs/containerd/cri/containerd-cri-presubmit-jobs.yaml
56:          --gcp-project=cri-c8d-pr-node-e2e

config/jobs/kubernetes/generated/generated.yaml
26:      - --gcp-project=ubuntu-image-validation
64:      - --gcp-project=ubuntu-image-validation
104:      - --gcp-project=ubuntu-image-validation
142:      - --gcp-project=ubuntu-image-validation
182:      - --gcp-project=ubuntu-image-validation
220:      - --gcp-project=ubuntu-image-validation
260:      - --gcp-project=ubuntu-image-validation
298:      - --gcp-project=ubuntu-image-validation
338:      - --gcp-project=ubuntu-image-validation
376:      - --gcp-project=ubuntu-image-validation
416:      - --gcp-project=ubuntu-image-validation
454:      - --gcp-project=ubuntu-image-validation
494:      - --gcp-project=ubuntu-image-validation
532:      - --gcp-project=ubuntu-image-validation
572:      - --gcp-project=ubuntu-image-validation
610:      - --gcp-project=ubuntu-image-validation
651:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
697:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
743:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
782:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
822:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
862:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
901:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
941:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
981:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1020:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1060:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1100:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1139:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1179:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1219:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1258:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1298:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1338:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1377:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1417:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1457:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1496:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1536:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests
1576:      - --gcp-project=ubuntu-os-gke-cloud-dev-tests

config/jobs/kubernetes/sig-release/release-branch-jobs/1.19.yaml
1038:        - --gcp-project=k8s-jkns-pr-gce-gpus

config/jobs/kubernetes/sig-network/sig-network-misc.yaml
81:      - --gcp-project=k8s-e2e-gce-alpha-api-access
365:      - --gcp-project=k8s-jenkins-gce-gci-ip-aliases

config/jobs/kubernetes/sig-release/release-branch-jobs/1.17.yaml
886:        - --gcp-project=k8s-jkns-pr-gce-gpus

config/jobs/kubernetes/sig-release/release-branch-jobs/1.16.yaml
736:        - --gcp-project=k8s-jkns-pr-gce-gpus
1013:        - --gcp-project=k8s-presubmit-scale

config/jobs/kubernetes/sig-network/ingress-gce-e2e.yaml
246:      - --gcp-project=k8s-ingress-e2e-scale-backup

config/jobs/kubernetes/sig-release/release-branch-jobs/1.18.yaml
1087:        - --gcp-project=k8s-jkns-pr-gce-gpus

config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-presubmits.yaml
40:        - --gcp-project=k8s-jkns-gci-autoscaling

config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-config.yaml
181:      - --gcp-project=k8s-jkns-gci-autoscaling
207:      - --gcp-project=k8s-jkns-gci-autoscaling
241:      - --gcp-project=k8s-jkns-gci-autoscaling-migs
267:      - --gcp-project=k8s-jkns-gci-autoscaling-migs

config/jobs/kubernetes/sig-scalability/sig-scalability-presubmit-jobs.yaml
98:        - --gcp-project=k8s-presubmit-scale
206:        - --gcp-project=k8s-presubmit-scale
347:        - --gcp-project=k8s-presubmit-scale

config/jobs/kubernetes/sig-scalability/sig-scalability-periodic-jobs.yaml
233:      - --gcp-project=k8s-jenkins-blocking-kubemark
290:      - --gcp-project=kubemark-scalability-testing

config/jobs/kubernetes/sig-scalability/sig-scalability-golang.yaml
70:      - --gcp-project=k8s-presubmit-scale

config/jobs/kubernetes/sig-scalability/sig-scalability-release-blocking-jobs.yaml
30:      - --gcp-project=kubernetes-scale
80:      - --gcp-project=kubernetes-scale

config/jobs/kubernetes/sig-cloud-provider/gcp/gpu/gpu-gce.yaml
77:      - --gcp-project=k8s-infra-e2e-gpu-project

config/jobs/kubernetes/sig-cloud-provider/gcp/gpu/gcp-gpu-presubmits.yaml
45:        - --gcp-project=k8s-jkns-pr-gce-gpus

config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml
888:      - --gcp-project=k8s-jkns-e2e-gce-ubelite
916:      - --gcp-project=k8s-jkns-gce-gci-soak
946:      - --gcp-project=k8s-jkns-gce-soak-1-6
976:      - --gcp-project=k8s-jkns-gci-gce-soak-1-4
1005:      - --gcp-project=k8s-jkns-gci-gce-soak-1-7
1034:      - --gcp-project=k8s-jkns-gci-gce-soak-1-6

config/jobs/kubernetes/sig-cloud-provider/gcp/gce-misc.yaml
17:      - --gcp-project=kubernetes-ha-master

config/jobs/kubernetes/sig-api-machinery/sig-api-machinery-config.yaml
108:        - --gcp-project=k8s-network-proxy-e2e

config/jobs/kubernetes/sig-node/containerd.yaml
269:      - --gcp-project=cri-containerd-node-e2e
299:      - --gcp-project=cri-containerd-node-e2e
329:      - --gcp-project=cri-containerd-node-e2e
359:      - --gcp-project=cri-containerd-node-e2e
392:      - --gcp-project=k8s-jkns-e2e-gci-gce-soak-1-4
786:      - --gcp-project=cri-containerd-node-e2e
816:      - --gcp-project=cri-containerd-node-e2e
846:      - --gcp-project=cri-containerd-node-e2e
931:      - --gcp-project=cri-containerd-node-e2e
960:      - --gcp-project=cri-containerd-node-e2e

config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml
143:        - --gcp-project=k8s-jkns-pr-node-e2e
179:            - --gcp-project=k8s-jkns-pr-node-e2e
213:            - --gcp-project=k8s-jkns-pr-node-e2e
247:            - --gcp-project=k8s-jkns-pr-node-e2e
284:        - --gcp-project=k8s-jkns-pr-node-e2e

config/jobs/cadvisor/cadvisor.yaml
40:        - --gcp-project=cadvisor-e2e
96:      - --gcp-project=ci-cadvisor-e2e

/unshrug
/sig node
A number of the jobs that still pin are sig-node jobs. I don't know if there's something special about those projects, but I know we've successfully migrated a few node e2e projects to use the standard gce-project pool boskos offers up
/sig scalability
/sig network
/sig autoscaling
based on some of the other paths

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 added sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. and removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. ¯\_(ツ)_/¯ ¯\\\_(ツ)_/¯ labels Sep 11, 2020
@fejta-bot
Copy link

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-testing, kubernetes/test-infra and/or fejta.
/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 Dec 10, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 9, 2021
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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.

@spiffxp
Copy link
Member

spiffxp commented Feb 8, 2021

/remove-lifecycle rotten
/reopen
/priority backlog
/lifecycle frozen
These should be addressed while migrating kubernetes CI away from google.com gcp projects (ref: kubernetes/k8s.io#1469). If there's no need for a special project, just switch to --gcp-project-type=gce

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Feb 8, 2021
@k8s-ci-robot
Copy link
Contributor

@spiffxp: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen
/priority backlog
/lifecycle frozen
These should be addressed while migrating kubernetes CI away from google.com gcp projects (ref: kubernetes/k8s.io#1469). If there's no need for a special project, just switch to --gcp-project-type=gce

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 Feb 8, 2021
@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 Feb 8, 2021
@spiffxp
Copy link
Member

spiffxp commented Feb 26, 2021

/help

@k8s-ci-robot
Copy link
Contributor

@spiffxp:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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 added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Feb 26, 2021
@SergeyKanzhelev SergeyKanzhelev moved this from Triage to Issues - To do in SIG Node CI/Test Board Nov 10, 2021
@mmiranda96
Copy link
Contributor

/unassign @amwat

Hi Amit, I'm unassigning you from this so someone else can take it, feel free to take it again if you plan to work on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/boskos Issues or PRs related to code in /boskos help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
Status: Issues - To do
Development

No branches or pull requests

10 participants