#kubectl explain tridentorchestrator

1 messages · Page 1 of 1 (latest)

brittle panther
#

Any plans to add “normal” operator documentation to be displayed using “explain”?

Have customers deploying trident expecting this fairly standard operator behavior beyond an empty document.

If not planned, I’d like to raise this as a formal feature request.

marsh carbon
brittle panther
#

I will suggest that then. The existing documentation is not the issue. Rather the nature of how it’s presented is. The customer has extensive experience in the K8S ecosystem, which includes the expectation that the “explain” functionality works in the “usual” K8S way for operators.

#

It’s much more that all the other operators they use present their docs in the same self contained way - no need to leave the K8S environment to find it and search through the sections (admittedly sometimes confusing to find some info bouncing section to section) instead of being able to double check parameters and examples right within K8S with “explain”

#

And to be fair, where there is a standard means in a large ecosystem any project should look to following those accepted practices as a default pattern.