DOCS-1021: Attempting to add autoyaml docs for Helm charts

[ravindk89]

Part of supporting minio/docs#1021

Summary

We've had an increase of requests for guidance in deploying via Helm.

This attempts to formalize the documentation structure for the Values.yaml in a format that can be automatically parsed by Sphinx into some form of web documentation.

It also attempts to synchronize some of the functionality between the Chart and the CRD.

Before merging either of these, we need to validate that the chart deployment itself is unaffected by the comments.

I've left comments for those areas which were unclear in their functionality.

[ravindk89]

@pjuarezd @cniackz let me know what you think of the above.

[cniackz]

Let's have test passing to approve it:

Change the version accordingly for image to be found within the cluster
Error: bad file '/home/runner/work/operator/operator/testing/../helm/operator/values.yaml': yaml: line 163: did not find expected key
Error: bad file '/home/runner/work/operator/operator/testing/../helm/operator/values.yaml': yaml: line 163: did not find expected key
Error: bad file '/home/runner/work/operator/operator/testing/../helm/operator/values.yaml': yaml: line 163: did not find expected key
Error: bad file '/home/runner/work/operator/operator/testing/../helm/operator/values.yaml': yaml: line 163: did not find expected key

[ravindk89]

OK @pjuarezd if this looks good we can merge it here, and I can finish the import work on the actual docs PR. Assuming all changes work.

[pjuarezd]

OK @pjuarezd if this looks good we can merge it here, and I can finish the import work on the actual docs PR. Assuming all changes work.

Looks good to me, we need another approver to merge tho

[ravindk89]

#1852 should resolve the testing errors.

[pjuarezd]

#1852 should resolve the testing errors.

that PR is merged already, could you rebase please @ravindk89?

[feorlen]

A couple typos and a reword for your consideration. 🚀

[qtomato3]

Please revise this change. I couldn't find any usage of .Values.existingSecret in tenant Helm templates. There's usage of .Values.secrets.existingSecret instead.