-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move prow jobs to use the community clusters #1273
Comments
hey @aramase do you know why the changes from kubernetes/test-infra#29473 prevented the jobs from finishing? There are a lot of folks that are going to be making this transition and your implementation looked pretty on track with what I'd expect. |
@aramase based on https://monitoring-eks.prow.k8s.io/d/96Q8oOOZk/builds?orgId=1&var-org=kubernetes-sigs&var-repo=secrets-store-csi-driver&var-job=pull-secrets-store-csi-driver-lint&var-build=All&from=1686575114078&to=1686578965140, it looks like the resource quotas should be significantly increased. Recommendations from @xmudrii would be 2-4 CPU and 4-8 GB Mem for linting jobs. If you merge with new capacity values, you should be able to monitor the above dashboard to see how it's performing. |
@rjsadow I'm happy to try the new resource limits and this issue was opened so we can follow up and move the jobs. The revert was done to unblock our patch release.
It might be good to document these recommendations for future reference. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
xref: kubernetes/test-infra#29722
The text was updated successfully, but these errors were encountered: