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

[Umbrella Issue] Migrate remaining prow jobs to community clusters #31789

Closed
16 tasks done
rjsadow opened this issue Feb 1, 2024 · 17 comments · Fixed by #31806 or #31812
Closed
16 tasks done

[Umbrella Issue] Migrate remaining prow jobs to community clusters #31789

rjsadow opened this issue Feb 1, 2024 · 17 comments · Fixed by #31806 or #31812
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. 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. 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

@rjsadow
Copy link
Contributor

rjsadow commented Feb 1, 2024

This is a continuation of:

There are only a few remaining jobs that are eligible to be migrated to the community clusters (aside from kops). We'll use this issue to track specific jobs that are remaining, their status, and hopefully close them all out.

If people are interested to work on this, Please pick one repo at the time and tag @ameukam in the PR for review.
Multiple attempts to migrate are completely OK. we are not expecting people to be successful on the first try.


Remaining Jobs

sig-storage

k8s.io

release

ingress-gce

perf-tests

  • pull-perf-tests-clusterloader2-e2e-gce-scale-performance-manual | Search Results |

sig-windows
- [ ] ci-kubernetes-e2e-windows-containerd-gce-master | Search Results |
- [ ] ci-kubernetes-e2e-windows-win2022-containerd-gce-master | Search Results |

sig-apps

sig-scalability

csi

sig-testing

sig-node

kubernetes

sig-cluster-lifecycle

sig-cloud-provider

@rjsadow rjsadow added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Feb 1, 2024
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 1, 2024
@rjsadow
Copy link
Contributor Author

rjsadow commented Feb 1, 2024

/sig testing
/sig k8s-infra

@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. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 1, 2024
@ameukam
Copy link
Member

ameukam commented Feb 1, 2024

/help wanted
/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@ameukam:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

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

In response to this:

/help wanted
/good-first-issue

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 good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Feb 1, 2024
@ameukam
Copy link
Member

ameukam commented Feb 1, 2024

If people are interested to work on this, Please pick one repo at the time and tag me in the PR for review.
Multiple attempts to migrate are completely OK. we are not expecting people to be successful on the first try.

@neolit123
Copy link
Member

kubeadm

pull-kubeadm-kinder-verify | Search Results |
pull-kubeadm-kinder-upgrade-latest | Search Results |

there were canaries for these at the comm cluster but they failed to start pods, so we ended up removing them.

@rjsadow
Copy link
Contributor Author

rjsadow commented Feb 1, 2024

@neolit123 is there a plan to retry moving them?

@neolit123
Copy link
Member

neolit123 commented Feb 1, 2024

@neolit123 is there a plan to retry moving them?

not currently, but if they are not flaky or throw immediate pod errors we can just swap.
PRs welcome for test-infra, can then be verified with a PR for k/kubeamd/kinder (minimal diff) on presubmit.

@sandipanpanda
Copy link
Member

Hi! I would like to take this opportunity to contribute to K8s. I'll pick kubernetes/kubernetes#123079

@prashantrewar
Copy link
Contributor

prashantrewar commented Feb 2, 2024

Hey, I would like to work on the release issue. I'll pick [pull-perf-tests-clusterloader2-e2e-gce-scale-performance-manual]

@kaitoii11
Copy link
Contributor

Hi, I'd like to work on ci-kubernetes-e2e-scalability-cleanup .

@alessandrocapanna
Copy link
Contributor

alessandrocapanna commented Feb 4, 2024

I'm moving ci-kubernetes-storage-scalability

@alessandrocapanna
Copy link
Contributor

I'm moving also ci-kubernetes-kubemark-100-gce-scheduler-highqps job

@ameukam
Copy link
Member

ameukam commented Feb 5, 2024

/open

@reetasingh
Copy link
Contributor

I will be working on #31793

@sawsa307
Copy link
Contributor

sawsa307 commented Feb 9, 2024

@rjsadow Hi Ricky migration for ingress-gce is done here #31846. We can mark it as done now. Thank you!

@ameukam
Copy link
Member

ameukam commented Jul 26, 2024

I think we are done here.

Thank you to everyone involved to make this happen!!! 🎉 🎉 🎉 🎉

/close

@k8s-ci-robot
Copy link
Contributor

@ameukam: Closing this issue.

In response to this:

I think we are done here.

Thank you to everyone involved to make this happen!!! 🎉 🎉 🎉 🎉

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. 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. 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
10 participants