search

kubernetes-sigs / secrets-store-csi-driver

Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
https://secrets-store-csi-driver.sigs.k8s.io/
Apache License 2.0
1.24k stars 289 forks source link

Move prow jobs to use the community clusters #1273

Open aramase opened 1 year ago

aramase commented 1 year ago

xref: https://github.com/kubernetes/test-infra/issues/29722

rjsadow commented 1 year ago

hey @aramase do you know why the changes from https://github.com/kubernetes/test-infra/pull/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.

rjsadow commented 1 year ago

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

aramase commented 1 year ago

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

Recommendations from @xmudrii would be 2-4 CPU and 4-8 GB Mem for linting jobs.

It might be good to document these recommendations for future reference.

k8s-triage-robot commented 7 months ago

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

aramase commented 7 months ago

/remove-lifecycle stale

k8s-triage-robot commented 4 months ago

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

k8s-triage-robot commented 3 months ago

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

aramase commented 3 months ago

/remove-lifecycle rotten /lifecycle frozen