Migrate k8s-infra-prow-build boskos/jobs away from k8s-infra-gce-project to gce-project

[spiffxp]

I originally had k8s-infra-prow-build use a boskos pool of type k8s-infra-gce-project to make it display as a distinct pool in https://monitoring.prow.k8s.io/d/wSrfvNxWz/boskos-resource-usage?orgId=1

This meant migrating an e2e job over to k8s-infra-prow-build involved:

• set cluster: k8s-infra-prow-build
• add a --gcp-project-type=k8s-infra-gce-project flag in the right place in the argument list

I've since added support for per-instance pools (ref: #17724) so we could go back to gce-project and still have it displayed in its own pool in the boskos dashboard.

Once this is done, migrating an e2e job to k8s-infra-prow-build will just be:

• set cluster: k8s-infra-prow-build

This will reduce the overhead of migrating release-blocking and merge-blocking jobs over to k8s-infra-prow-build

[spiffxp]

/assign

[spiffxp]

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

[spiffxp]

OK, looks like k8s-infra-gce-pool has dropped to zero, going to merge to gce-project

https://monitoring.prow.k8s.io/d/wSrfvNxWz/boskos-resource-usage?orgId=1

[spiffxp]

Holding open until I can see the increase in capacity for GCE project (k8s-infra). Turns out kubernetes/k8s.io#1088 hadn't taken effect last week. Did some poking, should see results soon

[spiffxp]

/close

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close

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.