Thank you very much for working on this @SgtCoDFish !

Should we make the same change in the periodic? Apart from that happy to lgtm

Good suggestion, thanks @irbekrm - not sure how I missed that.

I've added a second commit which does that and also which reduces the resource requirements which seemed high. Does that look reasonable? 😁

Thanks @SgtCoDFish !

For the resource requirements, I would slightly prefer if we re-evaluated what proportion of node resources each test type needs + whether we could, for example benefit from a different node size (as there probably have been some changes in that now that we use make) + monitor for possible flakes in one single PR so that all the reasoning etc is in one place.
At the moment the resource requiremement for each job that spins up kind cluster is ~50% of a node so that no more than 2 such jobs get allocated to that node.

Adding a hold if you agree else happy for it to go in as is

/hold
/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irbekrm, SgtCoDFish

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

The pull request process is described here

@irbekrm I've reverted the resource changes - I agree that it's probably better to attack them all in one go, yeah.

Thanks @SgtCoDFish and thanks for working on this!

/hold cancel
/lgtm

@SgtCoDFish: Updated the job-config configmap in namespace default at cluster default using the following files:

• key cert-manager-periodics.yaml using file config/jobs/cert-manager/cert-manager/cert-manager-periodics.yaml
• key cert-manager-presubmits.yaml using file config/jobs/cert-manager/cert-manager/cert-manager-presubmits.yaml