-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 remaining sig-testing
jobs to community clusters
#31793
Comments
sig-testing
jobs to community clusters
/help |
@ameukam: GuidelinesPlease ensure that the issue body includes answers to the following questions:
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 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. |
/assign. I will like to work on this |
/assign I want to work on remaining tasks. |
unable to migrate ci-kubernetes-e2e-gce-canary refer #31910 |
okay |
@reetasingh Let remove the test instead. I have approval from SIG testing to remove it. |
@rjsadow I confused jobs. 😓 |
@ameukam for job |
@reetasingh migrate it. |
Hi @anshikavashistha can you reopen your PR https://github.com/kubernetes/test-infra/pull/31895/files? looks like we still need it cc @ameukam |
We probably need to track separately the "at risk" sig testing jobs, KETTLE is probably something we should migrate but it requires migrating the GCP infra as well not just the job ... some of the others we might spin down |
The following jobs still run on the default google owned cluster and need to be migrated to a community cluster
sig-testing
- [ ] ci-kubernetes-e2e-gce-canary | Search Results |/sig testing
/sig k8s-infra
/kind cleanup
The text was updated successfully, but these errors were encountered: