operator Missing docs and functionality for Declarative users of the Operator

Missing docs and functionality for Declarative users of the Operator

Open snarlysodboxer opened this issue 2 years ago • 5 comments

It seems to me there's a huge bias in the operator docs and even functionality towards imperative usage of the operator. To each their own I guess but IMO imperative usage defeats most of the purpose of the operator. - If I wanted to imperatively configure minio instances, I'd just run it directly and then configure it.

For example, googling and the docs would lead you to believe the operator supports auto PVC cleanup, which it does but only imperatively through the darn krew plugin, which of course does not work for GitOps or ArgoCD type workflows, or even just ephemeral testing instances. 👎

Expected Behavior

Docs on declarative usage exist and can be easily found.
Ability to declare a complete setup, and not have to run a declared Job to run mc commands to configure the minio.
Ability to choose to have the operator not bother with anything related to running the console.
Ability to optionally get the deletion a Tenant to cause full cascading deletion including the PVCs.

Context

How has this issue affected you?

We are looking at alternatives, including the possibility of creating and contributing a separate operator for those who just want a simple way to fully declaratively manage minio instances in k8s, without the use of any kubectl plugins.
There's a lot of complexity and functionality and GUI in this operator that we will never want or need, and I get the picture that's true for a lot of others as well.
- A large percentage of the functionality seems to be built into the krew plugin instead of the operator itself, and that obviously doesn't work for many organizations.
We also get the feeling from #1100 and similar issues that the maintainers are not very interested in supporting the declarative approach?