prowjob CRD is too large to apply

[BenTheElder]

We're including all of the descriptions of pod fields in the embedded podspec, I think we can just drop those and have a single top level description pointing to the upstream pod type?

see: kubernetes/kubernetes#54579 (comment)

cc @jpbetz

the CRD is in https://github.com/kubernetes-sigs/prow/blob/main/config/prow/cluster/prowjob-crd/prowjob_customresourcedefinition.yaml

We ran into this while spinning up the new k8s infra instance today.

It looks like SSA is being used as a workaround:
https://github.com/kubernetes/test-infra/blob/ccb09026bddecdc4ff7089f34027897d0e764d5d/config/prow/Makefile#L35

[matthyx]

cross linking previous issue #181

[xrstf]

It's ugly and brute force, but one could also strip all descriptions from the YAML.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale