fix(pvc): Switch storage data to ReadWriteMany

[maximiliend]

ReadWriteOnce block PVC scheduling as it is used in multiples deployments

[jdenquin]

I would recommend to use S3 for storage instead of PVC with RWM (this is not a standard configuration)

[maximiliend]

Yes I strongly agree that a S3 (cloud or selfhosted) is better for this kind of usages !

But in the current chart version the PVC is mounted by several deployments at the same time. So the helm install cannot succeed with default values because some pods are stuck in waiting for the pvc that cannot be mounted more than once.

Maybe I am missing something or default behavior should be more oriented for a S3 usage with an example ond default configuration oriented on this ?

I think most people expect a chart to be ready to work with minimal configuration.

I am testing with RWX and if I have enough time I will switch to S3 to evaluates required changes in this chart.

[jdenquin]

Yes I have to add Minio as a dependecy to support a S3 configuration and avoid using a PVC

[electrosenpai]

Yes I strongly agree that a S3 (cloud or selfhosted) is better for this kind of usages !

But in the current chart version the PVC is mounted by several deployments at the same time. So the helm install cannot succeed with default values because some pods are stuck in waiting for the pvc that cannot be mounted more than once.

Maybe I am missing something or default behavior should be more oriented for a S3 usage with an example ond default configuration oriented on this ?

I think most people expect a chart to be ready to work with minimal configuration.

I am testing with RWX and if I have enough time I will switch to S3 to evaluates required changes in this chart.

Hi @maximiliend ,

Thank you for your detailed feedback and insights regarding the PVC scheduling issue. We completely agree that an S3-compatible storage solution is much better suited for this use case.

We wanted to let you know that we've recently implemented MinIO as an optional dependency in the chart, which provides an S3-compatible self-hosted solution. This should address the issue you're describing with ReadWriteOnce PVCs, as MinIO allows for greater flexibility without the limitations of single attachment on multiple deployments.

You can now switch to an S3 setup with minimal configuration, and we believe this will meet your expectation for a "ready to use" chart with minimal setup.

Please feel free to give it a try and let us know if this resolves your use case or if you have any further suggestions!

Thanks again for your contributions and for pushing the discussion forward.