CEL for CRD AdditionalPrinterColumns

[sreeram-venkitesh]

Enhancement Description

• One-line enhancement description (can be used as a release note): Provide a more powerful way to express human readable printer columns exposed by CRDs than simple JSON paths.
• Kubernetes Enhancement Proposal: KEP 4595: CEL for CRD AdditionalPrinterColumns #4602
• Discussion Link: https://docs.google.com/document/d/1V8mo6tbApM8o1ZrYcJBms95oVojxCnIi-EomWupEPp8/edit?usp=sharing
• Primary contact (assignee): @sreeram-venkitesh
• Responsible SIGs: api-machinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP 4595: CEL for CRD AdditionalPrinterColumns #4602
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[sreeram-venkitesh]

/sig api-machinery

[kannon92]

@sreeram-venkitesh really looking forward to this feature!

We ran into this for JobSet and it would be great to have something like this!

[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

[msvticket]

/remove-lifecycle stale