prow icon indicating copy to clipboard operation
prow copied to clipboard
verified publisher icon kubernetes-sigs

prowjob CRD is too large to apply

Open BenTheElder opened this issue 1 year ago • 5 comments

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: https://github.com/kubernetes/kubernetes/issues/54579#issuecomment-2014891144

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

BenTheElder avatar Aug 21 '24 18:08 BenTheElder

cross linking previous issue https://github.com/kubernetes-sigs/prow/issues/181

matthyx avatar Aug 22 '24 05:08 matthyx

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

xrstf avatar Oct 13 '24 14:10 xrstf

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

k8s-triage-robot avatar Jan 11 '25 15:01 k8s-triage-robot

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:

  • 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Feb 10 '25 15:02 k8s-triage-robot

/lifecycle frozen

BenTheElder avatar Feb 10 '25 18:02 BenTheElder