ProwJob CRD is too large about prow HOT 5 CLOSED

Hi @maboehm does it work if you kubectl create -f ... instead?
I think the main difference is that apply also saves the last applied configuration in the annotations, which doubles the size required and can more easily trigger the etcd limit.

from prow.

kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/prow/main/config/prow/cluster/prowjob-crd/prowjob_customresourcedefinition.yaml --server-side

(apparently it doesn't, sorry)

from prow.

Either way, since tools like Helm or Flux use apply the size should work for that as well.

from prow.

I have been using apply --server-side=true to avoid the annotation. It looks like the CRD itself is finally too large. With server side apply it worked up until e67659d (including). From 6405295 it is no longer possible to apply.

The only way to avoid this is to reduce the size of the CRD or configure etcd to allow a larger size. 🙁

from prow.

ok well I think we have to shrink it... @maboehm wanna have a try?

from prow.