Kubectl explain does not work on CRD

[harpratap]

The jaegers.jaegertracing.io API returns empty when doing kubectl explain jaeger
But it should return at least the spec, if not also the description.

I understand the reasoning behind removing the descriptions in #932 but an alternative should be provided where it is easy to read the entire API definition with explanation like in kubectl explain or in the way Istio does this for their operator - https://istio.io/docs/reference/config/istio.operator.v1alpha1/

[objectiser]

@harpratap Would you be interested in contributing a PR to fix this?

[izelnakri]

Hi there, yes this feature is absolutely needed. I'm currently confused on where to look for the Jaeger CRD API, wanted to check all the storage configurations but stuck because kubectl explain Jaeger.spec.storage returns empty description.

[izelnakri]

What is suggested here will increase use when implemented, and it will help finding bugs as well, I think I found one with cassandra storage for example.

[objectiser]

@izelnakri This is probably due to the description fields being stripped from the CRD, which was necessary due to its size - when using kubectl apply it failed. See #854.

[esnible]

The structure seems visible when I do kubectl explain jaeger or kubectl explain jaeger.spec or kubectl explain jaeger.spec.collector.

The description fields are not present. Is this Issue a request for field descriptions, or do you not see the structure at all?