Kubernetes ReadWriteOnce limitations

Not allowing ReadWriteMany in the Digital Ocean CSI AND not allowing users to persist storage ( is extremely limiting.

As an example, i’d like to populate data within our persistent volumes, however only being able to attach one PersistentVolumeClaim to a pod means we can’t attach a temporary container to a PVC to “fill it”.

Since the only storage class is “reclaimPolicy: Delete”, we also can’t “pre-fill” PVC’s before the infrastructure is created.

Are there any plans to fix these limitations? In theory we should be able to attach as many pods to a ReadWriteMany PVC as we want as long as they are all kept on the same node in the node pool… however the digital ocean csi prevents that as well.

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
February 9, 2022

Hey @haikuinc,

Indeed, this is currently a limitation on how the block storage works:

Attaching your PVC to multiple pods would only work if your pods are scheduled on a single Node, as this is where physically the volume would be attached on.

The best thing to do to get your voice heard regarding this would be to head over to our Product Ideas board and post a new idea, including as much information as possible for what you’d like to see implemented.

An alternative approach is to use an S3 storage like the DigitalOcean Spaces, that way you can read and write to a single bucket from multiple pods.

Hope that helps! - Bobby.