-
Notifications
You must be signed in to change notification settings - Fork 553
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
[Test] check if cephcsi is having any issue to support multiple accessModes. #4853
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
Tried with below possible combinations -
we have this check for RWO here - ceph-csi/internal/util/validate.go Lines 88 to 99 in d8a0407
probably, we need to remove this check or tweak the condition to allow above combination? |
ROX is only supported for clone from PVC or clone from snapshot not for a fresh PVC because its empty PVC and of no use for read only mode. |
I agree, but now that we aim to support multiple access modes, this condition is no longer relevant. What about a PVC with both ROX and RWO access modes, where one pod writes data while others access it as read-only? 🤔 |
The kubernetes access needs to be translated into CSI specification, AFAIK we don't have such a cap in csi spec, if we have one we need to support it as well. ROX translates to |
https://github.com/kubernetes-csi/csi-lib-utils/blob/master/accessmodes/access_modes.go might help you to translate kube access to CSI spec |
Kubernetes and the CSI spec support creating a volume with multiple accessModes, check if cephcsi is already supporting it or not and see if there are any issues with the supports, if it's supported and don't have any issues we need to add E2E testing for the same.
The text was updated successfully, but these errors were encountered: