We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, attempting to specify ReadOnlyMany as the access mode results in the following error during mounting: MountVolume.SetUp failed for volume "fsx-volume" : kubernetes.io/csi: mounter.SetupAt failed: rpc error: code = InvalidArgument desc = Volume capability not supported It seems MULTI_NODE_READER_ONLY is missing from volumeCaps––are there plans to support this anytime soon?
Currently, attempting to specify ReadOnlyMany as the access mode results in the following error during mounting:
ReadOnlyMany
MountVolume.SetUp failed for volume "fsx-volume" : kubernetes.io/csi: mounter.SetupAt failed: rpc error: code = InvalidArgument desc = Volume capability not supported
It seems MULTI_NODE_READER_ONLY is missing from volumeCaps––are there plans to support this anytime soon?
MULTI_NODE_READER_ONLY
volumeCaps
kubernetes-sigs/aws-fsx-csi-driver#164
The text was updated successfully, but these errors were encountered:
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
lifecycle/rotten
You can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Sorry, something went wrong.
No branches or pull requests
kubernetes-sigs/aws-fsx-csi-driver#164
The text was updated successfully, but these errors were encountered: