Migrate merge-blocking jobs to dedicated cluster: pull-kubernetes-e2e-gce-network-proxy-http-connect #18854
Labels
area/jobs
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
What should be cleaned up or changed:
This is part of #18550
To properly monitor the outcome of this, you should be a member of k8s-infra-prow-viewers@kubernetes.io. PR yourself into https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml#L603-L628 if you're not a member.
Migrate pull-kubernetes-e2e-gce-network-proxy-http-connect to k8s-infra-prow-build by adding a
cluster: k8s-infra-prow-build
field to the job:NOTE: migrating this job is not as straightforward as some of the other #18550 issues, because:
/test <this-job-name>
on themOnce the PR has merged, note the date/time it merged. This will allow you to compare before/after behavior.
Things to watch for the job
pull-kubernetes-e2e-gce-network-proxy-http-connect
for 6hpull-kubernetes-e2e-gce-network-proxy-http-connect
for 6hThings to watch for the build cluster
Keep this open for at least 24h of weekday PR traffic. If everything continues to look good, then this can be closed.
/wg k8s-infra
/sig testing
/area jobs
/help
The text was updated successfully, but these errors were encountered: