You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe
It looks like that currently it's not possible to define a priority of a printer column during CRD generation, i.e. all the generated additionalPrinterColumns have a default priority of 0. I would like some printer columns to have a non-zero priority so that they'll appear only in the wide view (using the -o wide flag).
Reference https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#priority
Describe the solution you'd like
I want to include a priority field in the PrinterColumn annotation. If possible I would like to work on this, I think this is not a very difficult task and also a good exercise to start contributing.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
* add priority field to the PrinterColumn
* fix code style & update docs
* set default value for priority
* fix crd generator test
* fix decorator equals
Is your enhancement related to a problem? Please describe
It looks like that currently it's not possible to define a priority of a printer column during CRD generation, i.e. all the generated
additionalPrinterColumns
have a default priority of 0. I would like some printer columns to have a non-zero priority so that they'll appear only in the wide view (using the-o wide
flag).Reference https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#priority
Describe the solution you'd like
I want to include a
priority
field in thePrinterColumn
annotation. If possible I would like to work on this, I think this is not a very difficult task and also a good exercise to start contributing.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: