Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
Currently, the PVCs can only be mounted in ReadWriteOnce mode and therefore the PVCs cannot be shared across multiple pods
at a minimum, please give us a new storage class based on Spaces. the only available open-source CSI for spaces https://github.com/ctrox/csi-s3 is marked as experimental by the author.
As a workaround I am using the nfs client provisioner, which allows ReadWriteMany. But for this to work you have to run a nfs server on another pod or droplet storing the data. Having direct support from DO would be preferable.
This is a blocker for me too, would love to see this implemented.
Hi, I am working on the DOKS team.
Rolling upgrades should work as long as you make sure that a volume is not being attached by two pods on separate nodes. (If the pods run on the same node, they should all be able to mount the volume.)Previous Kubernetes releases had trouble moving volumes along as pods restarted and were scheduled on different nodes. More recent versions should not have this problem anymore.
I cannot use DO in my use case until this feature becomes available. Moving to Azure for now.
Interesting side-note to this limitation:
Rolling updates will not work, limiting your deployment strategy to "Recreate", which causes downtime.
Replicas of more than 1 will not work, as only one pod can attach to the storage at the same time.
For me this is really a massive limitation to using k8s on DO. I understand it's because of the nature of the Block Storage solution that DO has, but technical debt is not an excuse.
You won't be notified about changes to this idea.