Skip to content
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

Support for ReadOnlyMany in the volume mount in Pods #1162

Open
badri-pathak opened this issue May 13, 2024 · 0 comments
Open

Support for ReadOnlyMany in the volume mount in Pods #1162

badri-pathak opened this issue May 13, 2024 · 0 comments
Assignees
Labels
Type: Enhancement Indicates a request for feature to be improved.

Comments

@badri-pathak
Copy link
Member

badri-pathak commented May 13, 2024

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Look for the support of ReadOnlyMany in the volume mount in Pods. Need to look while mounting the volume in NodePublish call.

Currently, creation of volume if VolumeAccessMode is ReadOnlyMany is not allowed.

If the feature supports, we have to remove that restriction

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: scale-fset-pvc-1
  namespace: ibm-spectrum-scale-csi-driver
spec:
  accessModes:
  - ReadOnlyMany
  resources:
    requests:
      storage: 1Gi
```
@badri-pathak badri-pathak added the Type: Enhancement Indicates a request for feature to be improved. label May 13, 2024
@badri-pathak badri-pathak self-assigned this May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Indicates a request for feature to be improved.
Projects
None yet
Development

No branches or pull requests

1 participant