Make critical jobs Guaranteed Pod QOS: pull-kubernetes-verify

[spiffxp]

What should be cleaned up or changed:

This is part of #18530

The following jobs should be Guaranteed Pod QOS, meaning they should have CPU and memory resource limits, and matching resource requests:

• pull-kubernetes-verify

These jobs run on (google.com only) k8s-prow-build, so @spiffxp has provided the following guess:

• suggest 7 cpu, 10Gi mem

General steps to follow:

• update the job definitions in /config/jobs to have matching CPU and memory limits and requests
  • e.g. (ci-kubernetes-e2e-gci-gce has a resources: field with matching entries)
• open a pull request, include a link to this issue and cc @kubernetes/ci-signal in the description
• keep an eye on the jobs for the next few days, and if they start failing more than usual, open followup pull requests to raise resources
  • can look at recent prow.k8s.io runs (e.g. https://prow.k8s.io/?job=ci-kubernetes-e2e-gci-gce)
  • can look at job history (e.g. https://prow.k8s.io/job-history/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce)
  • can look at testgrid dashboards (e.g. https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-default)
• after the job has remained stable for a few days, declare victory

/sig testing
/sig release
/area jobs
/area release-eng

[hasheddan]

/assign

[spiffxp]

/remove-help
/assign @hasheddan
/reopen
Holding open to verify the job is healthy after some soak time

[k8s-ci-robot]

@spiffxp: Reopened this issue.

In response to this:

/remove-help
/assign @hasheddan
/reopen
Holding open to verify the job is healthy after some soak time

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.

[spiffxp]

So far so good

Thought I'd found some suspicious runs in #18610 (comment) but agree with @hasheddan they're expected behavior for PRs that have been force-pushed (abort any previously running jobs, trigger new ones to pick up the new commit)

[spiffxp]

/remove-help

[hasheddan]

Looks like a timeout on this run. See kubernetes/kubernetes#93387 (comment)

[RobertKielty]

/close

[k8s-ci-robot]

@RobertKielty: 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.