-
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
[Umbrella issue] Move prowjobs to k8s-infra-prow-build #30277
Comments
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 |
Related to: - kubernetes#30277 Move some prowjobs to k8s-infra-prow-build Signed-off-by: Arnaud Meukam <[email protected]>
Related to: - kubernetes#30277 Signed-off-by: Arnaud Meukam <[email protected]>
Related to: - kubernetes#30277 Signed-off-by: Arnaud Meukam <[email protected]>
Related: - kubernetes#30277 Signed-off-by: Arnaud Meukam <[email protected]>
Related to: - kubernetes#30277 Signed-off-by: Arnaud Meukam <[email protected]>
Related to: - kubernetes#30277 Signed-off-by: Arnaud Meukam <[email protected]>
Related to: - kubernetes#30277 Migrate pull-kubernetes-e2e-gce-device-plugin-gpu to the community cluster. Signed-off-by: Arnaud Meukam <[email protected]>
Related to: - kubernetes#30277 Move alpha and canary prowjobs to GKE cluster k8s-infra-prow-build Signed-off-by: Arnaud Meukam <[email protected]>
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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-sigs/prow repository. |
We have other tracking issues, and we're not necessarily moving them to k8s-infra-prow-build |
Move all the prowjobs running on the
default
cluster tok8s-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:
/sig testing
/sig k8s-infra
The text was updated successfully, but these errors were encountered: