The requirement of persistent storage for Kubernetes has lead us to different implementations. At first, Kubernetes volume plugins were “in-tree”, meaning they’re linked, compiled, built, and shipped with the core kubernetes binaries. Adding support for a new storage system to Kubernetes (a volume plugin) required checking code into the core Kubernetes repository. And aligning with the Kubernetes release process is painful for many plugin developers.
On January 10, 2018 the k8s community introduced CSI. The goal of CSI is to establish a standardized mechanism for Container Orchestration Systems (COs) to expose arbitrary storage systems to their containerized workloads.
We aim to create a CSI driver for manila, in order to serve RXW storage leveraging the existing implementations for different storage backends.
Closing this RFE as there is no actual work to do in Manila per say. CSI development and testing is tracked on the OCP side. Any bug found in Manila will need a dedicated BZ.