-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Remove custom projects from SIG Node test manifests #23822
Comments
/cc @ameukam |
/assign |
We should firstly identity those master-{blocking,informing} and migrate them before the rest. |
Related: #23291 Don't ask for a node-e2e project, the default gce-project type should be enough |
/milestone v1.23 |
@ameukam I took a good look on this issue today, also rest of the issues and PRs that were mentioned. So we need to remove the listed projects from jobs, is that correct? |
We also want to migrate the release-blocking prowjobs to the community-owned build clusters by adding
to the spec of the prowjob.
I would advise doing a few jobs per PR so I can easily monitor the jobs after the flag is dropped and also to start with the periodics. @ehashman Ouf of curiosity, why do we need a specific bucket ( |
@ameukam I've raised a PR after identifying master-{blocking,informing} jobs to the community-owned build cluster. |
@rayandas |
@ameukam added sig-node release blocking jobs that needs to migrate to community-owned infrastructure. |
Hello @ameukam Now I got the requirements here. I just updated the PR for Though I need some clarification on this part, like how should I approach and that sort.
|
It's partially done. |
@rayandas: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
@ehashman Please reopen this issue. It's partially done. There will be two more PRs for this issue. |
/reopen |
@SergeyKanzhelev: Reopened this issue. In response to this:
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. |
/milestone v1.24 didn't quite finish this and now we're deep in freeze |
The last part is left now. /cc: @ameukam |
Quick inventory:
|
I will raise a PR to remove which are left. |
@ameukam Could you please shed some light on the third task here whenever you get time? |
@rayandas Looking at https://cs.k8s.io/?q=gs%3A%2F%2Fcri-containerd-testing&i=nope&files=&excludeFiles=&repos=, I think jobs stopped use |
@ameukam can this be closed? I think everything here we need to do is done? |
Some jobs still run on Google infrastructure : https://cs.k8s.io/?q=gcp-project%3Dcri-c8d-pr-node-e2e&i=nope&files=&excludeFiles=&repos= but there are related to Containerd. We can close it. |
/close |
@ehashman: Closing this issue. In response to this:
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. |
What should be cleaned up or changed:
SIG Infra has identified the following GCP projects that they'd like to retire:
SIG Node should remove these explicit projects from jobs wherever possible. A project should be automatically generated/selected. (see e.g. https://github.com/kubernetes/test-infra/pull/23777/files#diff-9495ba672589316a9265fd090ecb9c3c74fd414a11386acafda27df4bd409409)
Provide any links for context:
See also kubernetes/k8s.io#1469
/sig node k8s-infra
The text was updated successfully, but these errors were encountered: