Optimize resource usage of our prowjobs #2978
Assignees
Labels
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Comments
k8s-ci-robot
added
the
kind/cleanup
|
This PR got merged: /close |
|
@chrischdi: Closing this issue. In response to this:
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-sigs/prow repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to: kubernetes-sigs/cluster-api#10387
We should take a look at the jobs which run on community infra and adjust their cpu & memory resource reqests+limits.
/kind cleanup
Description
Reserving too much resources causes costs to the community which is why we should take a look and optimise our prowjob configurations.
The following dashboard from sig-test-infra helps to get a view on the current usage of the jobs:
https://monitoring-eks.prow.k8s.io/d/53g2x7OZz/jobs?orgId=1&var-org=kubernetes-sigs&var-repo=cluster-api-provider-vsphere&from=now-6h&to=now&var-job=All
The text was updated successfully, but these errors were encountered: