You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for this great project. I'm currently trying to deploy multiple instances of the minio operator. Unfortunately their privisioner https://github.com/minio/direct-csi doesn't support multiple storage classes when deploying multiple instances of it like this project does.
I'm wondering is it possible for this provisioner to create the pvs in each path of a config using round robin instead of at random? Then I could use this for everything which would be great.
The text was updated successfully, but these errors were encountered:
Thank you for this great project. I'm currently trying to deploy multiple instances of the minio operator. Unfortunately their privisioner https://github.com/minio/direct-csi doesn't support multiple storage classes when deploying multiple instances of it like this project does.
I'm wondering is it possible for this provisioner to create the pvs in each path of a config using round robin instead of at random? Then I could use this for everything which would be great.
Thanks for the idea and technically it's doable by having an extra layer to keep the path usage info. I will add to the backlog and see if any plan to do in the future.
Hi,
Thank you for this great project. I'm currently trying to deploy multiple instances of the minio operator. Unfortunately their privisioner https://github.com/minio/direct-csi doesn't support multiple storage classes when deploying multiple instances of it like this project does.
I'm wondering is it possible for this provisioner to create the pvs in each path of a config using round robin instead of at random? Then I could use this for everything which would be great.
The text was updated successfully, but these errors were encountered: