hypershift: Request higher resoures for unit test jobs

[csrwng]

Adding fuzzing tests to API conversion code[1] results in test pods timing out when running unit tests[2]. This PR bumps up the requirements for unit tests so they can actually complete:

[1] openshift/hypershift#1703
[2] https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_hypershift/1703/pull-ci-openshift-hypershift-main-unit/1566800257059131392

Resource requests are based on a successful run of unit tests on a standalone pod:

[enxebre]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: csrwng, enxebre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/hypershift/OWNERS [csrwng,enxebre]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@csrwng: Updated the following 2 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-hypershift-main.yaml using file ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml
• ci-operator-4.12-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-hypershift-release-4.12.yaml using file ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.12.yaml

Details

In response to this:

Adding fuzzing tests to API conversion code[1] results in test pods timing out when running unit tests[2]. This PR bumps up the requirements for unit tests so they can actually complete:

[1] openshift/hypershift#1703
[2] https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_hypershift/1703/pull-ci-openshift-hypershift-main-unit/1566800257059131392

Resource requests are based on a successful run of unit tests on a standalone pod:

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.