Provision stock e2e projects in anticipation of migrating kubernetes merge-blocking jobs

[spiffxp]

This is in anticipation of kubernetes/test-infra#18550

Based on visual inspection of https://monitoring.prow.k8s.io/d/wSrfvNxWz/boskos-resource-usage?orgId=1&from=now-90d&to=now

Source:

• Current k8s-prow-build boskos gce-project pool capacity is 200. Usage peaks just under 100.

Target:

• Current k8s-infra-prow-build boskos k8s-infra-gce-project pool capacity is 40. Usage peaks just under 30.

Goal:

• Add at least another 100 projects to k8s-infra-prow-build's boskos instance
• Add the new projects to a gce-project pool
• While doing this, merge the k8s-infa-gce-project pool into the gce-project pool, ref: Migrate k8s-infra-prow-build boskos/jobs away from k8s-infra-gce-project to gce-project test-infra#18552
  • Switch jobs away from k8s-infra-gce-project
  • Wait for k8s-infra-gce-project pool usage to be completely clean
  • Merge k8s-infra-gce-project pool into gce-project pool
• At the end of this, ensure boskos dashboard is setup to display the gce-project pool

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

[spiffxp]

/assign

[spiffxp]

I've added 40 thus far, so out of 100 that mean 60 remain. Going to add another 40, leaving 20.

It may be that as we're re-evaluating the full set of merge-blocking jobs for kubernetes (ref: kubernetes/test-infra#18729) we may lower demand for the gce-project resource

[spiffxp]

/close
OK, I think the gce-project pool is large enough for now.

Over the past 30 days we've migrated over all merge-blocking jobs for kubernetes/kubernetes on top of having migrated most of the release-blocking jobs earlier. We're going to have plenty of headroom for a while.

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close
OK, I think the gce-project pool is large enough for now.

Over the past 30 days we've migrated over all merge-blocking jobs for kubernetes/kubernetes on top of having migrated most of the release-blocking jobs earlier. We're going to have plenty of headroom for a while.

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.