Setting priority 0 in crd, breaks CD workflow

[sakomws]

By default, kubernetes not shows up priority field if it is 0, which breaks CD tooling, assuming its missing the field.

Would be great to remove the priority fields:

helm-charts/charts/hivemq-platform-operator/crds/hivemq-platforms.hivemq.com-v1.yml

Line 16 in 9929ffa

- additionalPrinterColumns:

here is screenshot from CD tool:

[afalhambra-hivemq]

Thanks @sakomws for reaching out to us.

In K8s for a CustomResourceDefinition (CRD), the additionalPrinterColumns columns with a 0 priority are shown in a standard view (kubectl get), however for non-0 priority columns are only shown when -o wide is passed.
See:

$ kubectl get hivemq-platforms.hivemq.com hivemq 
NAME       MESSAGE                              STATE         STATEPHASE
hivemq      HiveMQ Platform is ready            RUNNING       READY

$ kubectl get hivemq-platforms.hivemq.com platform -o wide
NAME       MESSAGE                              STATE         STATEPHASE
hivemq     HiveMQ Platform is ready             RUNNING       READY

So when you say kubernetes not shows up priority field if it is 0, what command are you using to display these columns?