-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rook block device not working for ReadWriteMany #88
Comments
I'm not sure what your use case is, whether you need a raw block volume or a filesystem volume, but if you need |
It is not the problem of Rook. You see that issue because PVC is Project/Namespace specific. And PV is available cluster wide accessible. |
That answer is just wrong and doesn't even make any sense at all. It has nothing todo with any namespaces and the OP already gave a hint on what's the issue. As @ericgraf pointed out in his comment, ceph-csi doesn't support ReadWriteMany for rbd volumes (most likely because rbd doesn't support it, which would make absolute sense given that it's block storage). This is not a rook issue and it won't be fixed by ceph either so this issue can be closed. |
Whe trying to create a
PersistentVolumeClaim
withReadWriteMany
, I get the following error when runningkubectl describe pvc <name>
:My
cluster:yml
:/dev/sdb
it works forReadWriteOnce
claims though, any ideas?(Also, can create a separate issue if needed, but might be worth updating the image used for the ingress controller as the nginx version in the default is fairly old, I used
k8s.gcr.io/ingress-nginx/controller:v0.45.0
as a drop-in replacement)The text was updated successfully, but these errors were encountered: