release-blocking jobs must run in dedicated cluster: ci-kubernetes-e2e-gce-device-plugin-gpu

[spiffxp]

Part of #18549

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

Once gpu-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]

Working on kubernetes/k8s.io#1095 first

[spiffxp]

/assign

[spiffxp]

/close
All jobs have run successfully since being migrated over

• https://testgrid.k8s.io/sig-release-master-blocking#gce-device-plugin-gpu-master&width=20
• https://testgrid.k8s.io/sig-release-1.19-blocking#gce-device-plugin-gpu-1.19&width=20
• https://testgrid.k8s.io/sig-release-1.18-blocking#gce-device-plugin-gpu-1.18&width=20
• https://testgrid.k8s.io/sig-release-1.17-blocking#gce-device-plugin-gpu-1.17&width=20
• https://testgrid.k8s.io/sig-release-1.16-blocking#gce-device-plugin-gpu-1.16&width=20

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close
All jobs have run successfully since being migrated over

• https://testgrid.k8s.io/sig-release-master-blocking#gce-device-plugin-gpu-master&width=20
• https://testgrid.k8s.io/sig-release-1.19-blocking#gce-device-plugin-gpu-1.19&width=20
• https://testgrid.k8s.io/sig-release-1.18-blocking#gce-device-plugin-gpu-1.18&width=20
• https://testgrid.k8s.io/sig-release-1.17-blocking#gce-device-plugin-gpu-1.17&width=20
• https://testgrid.k8s.io/sig-release-1.16-blocking#gce-device-plugin-gpu-1.16&width=20

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.