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
[manila-csi-plugin] If Manila CSI plugin supports Access Mode ReadWriteOnce #2564
Comments
we are not using manila, so difficult to answer this issue. But in general manila is readwritemany |
Hello @syy6, indeed the driver never supported this, and the mode validation is very relaxed because of historical reasons. We've never really seen too convincing use cases to get this implemented, but in any case it shouldn't be too hard if you only need attachment tracking within the cluster. See https://github.com/kubernetes-csi/external-attacher Note that the Manila service itself does not support attachments at the moment, and there would be nothing stopping other clients from accessing the share. |
Thanks @jichenjc @zetaab @gman0, we have a tricky issue here. |
What I'm curious is whether we need to implement changes listed here? |
Hi,
In our envrioment, we create Manila PV with Access Mode ReadWriteOnce as below
and we don't get any error message. But per our test, it seems the ReadWriteOnce doesn't reallt take effect, when a Pod A on Node M still are in Terminating status, another Pod B on Node N already can mount it and running.
We checked the code, VolumeCapability_AccessMode_SINGLE_NODE_WRITER(ReadWriteOnce) is mentioned, but it seems there is no real logic to control it in the manila-csi-plugin driver.
We also notice a document from OpenShift, actually OpenStack Manila only supports ReadWriteOncePod & ReadWriteMany.
Could U please help to check if Manila CSI plugin supports Access Mode ReadWriteOnce? If not, if there is any other way we can achieve the same function here? Thanks!
The text was updated successfully, but these errors were encountered: