Your ReadWriteMany (RWX) Storage in k8s with Manila CSI
summary
Manila CSI delivers dynamic RWX provisioning for Kubernetes by wiring the Manila controller plugin to Manila and a node plugin that proxies to existing CSI NFS/SMB drivers; deployment uses Helm charts or an OpenShift operator that auto-creates storageclasses (it syncs new Manila share types but does not delete removed classes). Demo provisions a PVC, creates a Manila share, runs three writer pods on two nodes that show real‑time shared writes. One limitation: one protocol per Manila CSI instance. Keystone-based tenant separation and ongoing performance and backup tests are in progress.
AI-written summary · about
chapters (7)
- 0:00Introduction to the topic
- 1:06Kubernetes storage and CSI
- 4:23Integration with OpenStack
- 7:21Understanding OpenStack Manila
- 12:45Deploying Manila CSI
- 16:10Usage and live demo
- 20:07Future work and Q&A
related talks
41mRWX Storage for Container Orchestrators with CephFS and Manila
25mConnecting ecosystems: How Cinder CSI, Ember CSI & Manila CSI leverage OpenStack bits in Kubernetes
25mDynamic Workloads need Dynamic Storage - using rook-ceph with k8s
44mImproving Storage Support in Apache Mesos using CSI
32mUnderstanding Kubernetes Storage: Getting in Deep by Writing a CSI Driver
32mCSI WON’T SAVE YOU - Why “CSI Support” is not a storage strategy and you are being setup to fail.
48mCSI in Kubernetes
35mHA and Data Mobility for persistent Volumes