-
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
jobs: pin ci-kubernetes-node-e2e-kubelet to spare project #17251
jobs: pin ci-kubernetes-node-e2e-kubelet to spare project #17251
Conversation
so we know it can work with boskos managed projects, but until we get a pool set aside for node jobs, I'd rather prevent them from using the pool used by most e2e jobs, in case a network ban happens again
/lgtm |
/hold cancel |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@spiffxp: Updated the
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. |
release-blocking jobs were already moved to a different GCP project in kubernetes#17251 and kubernetes#17257 due to network issues. This also moves the release-informing jobs away until new GCP project is created (ref: kubernetes/kubernetes#89892 (comment)). Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
so we know it can work with boskos managed projects, but until we get
a pool set aside for node jobs, I'd rather prevent them from using
the pool used by most e2e jobs, in case a network ban happens again
/cc @dims