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] Move prowjobs to k8s-infra-prow-build #30277

Closed
ameukam opened this issue Aug 2, 2023 · 9 comments
Closed

[Umbrella issue] Move prowjobs to k8s-infra-prow-build #30277

ameukam opened this issue Aug 2, 2023 · 9 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@ameukam
Copy link
Member

ameukam commented Aug 2, 2023

Move all the prowjobs running on the default cluster to k8s-infra-prow-build.

Currently, there is some difficulty to identify those running e2e tests on GCP.

Some of them uses specific credentials and are not eligilibe. Credentials are passed to those jobs are presets:

preset-do-credential-*
preset-aws-credential-*
preset-azure-*

/sig testing
/sig k8s-infra
@ameukam ameukam added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 2, 2023
@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. labels Aug 2, 2023
@rjsadow
Copy link
Contributor

rjsadow commented Aug 5, 2023

Is there a point where we should add a check to require new jobs to define a community cluster to use?

@ameukam
Copy link
Member Author

ameukam commented Aug 5, 2023

Is there a point where we should add a check to require new jobs to define a community cluster to use?

when we have no jobs running in the cluster default.

@rjsadow rjsadow mentioned this issue Aug 22, 2023
Open
54 tasks
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 15, 2023
@ameukam
capg: migrate prowjobs to k8s-infra-prow-build
ef3e25e 
Related to:
  - kubernetes#30277

Move some prowjobs to k8s-infra-prow-build

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam ameukam mentioned this issue Sep 15, 2023
Merged
@rjsadow rjsadow mentioned this issue Sep 16, 2023
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 19, 2023
@ameukam
migrate gcp pd driver to k8s-infra-prow-build
6833db6 
Related to:
  - kubernetes#30277

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam ameukam mentioned this issue Sep 19, 2023
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 19, 2023
@ameukam
migrate gcp firestore driver to k8s-infra-prow-build
817b460 
Related to:
  - kubernetes#30277

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam ameukam mentioned this issue Sep 19, 2023
Merged
@rjsadow rjsadow mentioned this issue Sep 19, 2023
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 20, 2023
@ameukam
Move kOps periodics to k8s-infra-prow-build
a70bf22 
Related:
 - kubernetes#30277

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 24, 2023
@ameukam
sig-cli: migrate prowjobs to community cluster
ddf2a8f 
Related to:
  - kubernetes#30277

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam ameukam mentioned this issue Sep 24, 2023
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 26, 2023
@ameukam
csi: move periodics to community cluster
f5064a1 
Related to:
  - kubernetes#30277

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam ameukam mentioned this issue Sep 26, 2023
Merged
@rjsadow rjsadow mentioned this issue Sep 27, 2023
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 29, 2023
@ameukam
gcp: migrate pull-kubernetes-e2e-gce-device-plugin-gpu
7443de9 
Related to:
  - kubernetes#30277

Migrate pull-kubernetes-e2e-gce-device-plugin-gpu to the community cluster.

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam ameukam mentioned this issue Sep 29, 2023
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Oct 6, 2023
@ameukam
csi: move alpha and canary to community cluster
687f20c 
Related to:
 - kubernetes#30277

Move alpha and canary prowjobs to GKE cluster k8s-infra-prow-build

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam ameukam mentioned this issue Oct 6, 2023
Closed
This was referenced Oct 18, 2023
Merged
Closed
Closed
Closed
Merged
Merged
This was referenced Oct 23, 2023
Merged
Merged
This was referenced Nov 11, 2023
Closed
Merged
Merged
Closed
Merged
This was referenced Jan 21, 2024
Merged
Merged
Merged
Merged
Merged
Merged
@k8s-triage-robot
Copy link

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-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 Jan 25, 2024
@ameukam
Copy link
Member Author

ameukam commented Jan 25, 2024

/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 Jan 25, 2024
This was referenced Jan 26, 2024
Merged
Open
@sawsa307 sawsa307 mentioned this issue Feb 6, 2024
Merged
@sawsa307 sawsa307 mentioned this issue Mar 12, 2024
Closed
9 tasks
@k8s-triage-robot
Copy link

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-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 24, 2024
@k8s-triage-robot
Copy link

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-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 May 24, 2024
@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 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 with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close not-planned

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 23, 2024
@BenTheElder
Copy link
Member

We have other tracking issues, and we're not necessarily moving them to k8s-infra-prow-build

#29722

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@BenTheElder @ameukam @rjsadow @k8s-ci-robot @k8s-triage-robot