release-blocking jobs must run in dedicated cluster: ci-kubernetes-e2e-gci-gce-ingress

[spiffxp]

Part of #18549

Need to figure out what special quotas "ingress-project" projects have: kubernetes/k8s.io#1093. Need google.com access to compare against the existing google.com projects, so can't make this a help-wanted

Once ingress-project is setup in k8s-infra-prow-builds' cluster, this should be a straightforward "set the cluster: field" PR

/sig testing
/sig release
/wg k8s-infra
/area jobs

[spiffxp]

/assign

[spiffxp]

Looks like ingress-project actually isn't needed for the release-blocking jobs? The canary ran just fine with default quotas. So a PR to move the release-blocking jobs, using default projects: #18734

[spiffxp]

Now that #18734 has merged (2020-08-07 2:01pm PT), keep an eye on the release-blocking jobs:

• https://testgrid.k8s.io/sig-release-master-blocking#gci-gce-ingress
• https://testgrid.k8s.io/sig-release-1.19-blocking#gce-cos-k8sbeta-ingress
• https://testgrid.k8s.io/sig-release-1.18-blocking#gce-cos-k8sstable1-ingress
• https://testgrid.k8s.io/sig-release-1.17-blocking#gce-cos-k8sstable2-ingress
• https://testgrid.k8s.io/sig-release-1.16-blocking#gce-cos-k8sstable3-ingress

[spiffxp]

/close
I've seen successful runs for everything but 1.16 and anticipate that will behave the same as the others

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close
I've seen runs for everything but 1.16 and anticipate that will behave the same as the others

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.