Add parameter to disable production-ready requirements

[patsys]

Is your feature request related to a problem? Please describe.

I'm not in a production environment, for example, a development or test environment, or in my case, a hobby project. I have three nodes, with two disks per node, but I cannot set two different storage classes to the pool to separate the disks, nor can I set a parameter to disable the minimum requirement of four disks for production readiness.

Describe the solution you'd like.

The best solution for me would be a parameter to disable the production requirements because I don't need Minio to be production-ready.

Describe any alternatives you've considered.

• In my case, it would be helpful to allow two different storage classes per storage pool. This wouldn't be necessary for my case, but it could help others.
• Don't use the operator and use a community helm chart.
• Fork it and add the parameter.

[ramondeklein]

Each pool will have a dedicated statefulset. Because of that, we cannot set different storage classes. Your solution can't be supported by operator and will never be.

In your situation, I would skip MinIO operator and just create three pods (so not a statefulset), so you can configure each PVC manually. Make sure you use proper hostnames, so you can still address the pods using the ellipsis notation. Of course you can mount the configuration secret to all three pods for easier configuration.

[patsys]

Hello @ramondeklein,

Thanks for the quick response.

The best solution that meets my requirements is to set the production-ready parameter to false and bypass the minimum requirement of four disks.

Another option is to allow more than one storage class in each pool. All pods should use the same storage classes. The problem is that when I set the storage to two, it creates two volumes per node (pod) on the same physical disk (one storageclass), and I cannot use my separate disks (two sraregeclass).

The follow disks used on all nodes:
Storageclass1 allocates on disk "sda"
Storageclass2 allocates on disk "sdb"

[ramondeklein]

We cannot support multiple storage classes for the reason listed above. Adding the option to use less than 4 disks will be abused in production. Either use MinIO in SNSD (single node/single disk) or use at least 4 disks. Other scenarios wont be supported using MinIO.

We don't support SNSD in operator, because it doesn't make any sense. It's more logical just to spin up a pod and PVC for that.