PLM needs to know what release; this feature is shipping in; at the point of writing this this feature has 8 FixVersions
If work for this feature was already delivered; we suggest that the remaining work be split off to its own feature and track to an upcoming release and this tracker be closed.
Provide CSI drivers to replace all the intree cloud provider drivers we currently have. These drivers will probably be released as tech preview versions first before being promoted to GA.
- Framework for rapid creation of CSI drivers for our cloud providers
- CSI driver for AWS EBS
- CSI driver for AWS EFS
- CSI driver for GCP
- CSI driver for Azure
- CSI driver for VMware vSphere
- CSI Driver for Azure Stack
- CSI Driver for Alicloud
- CSI Driver for IBM Cloud
|Framework for CSI driver||TBD||Yes|
|Drivers should be available to install both in disconnected and connected mode||Yes|
|Drivers should upgrade from release to release without any impact||Yes|
|Drivers should be installable via CVO (when in-tree plugin exists)|
Out of Scope
This work will only cover the drivers themselves, it will not include
- enhancements to the CSI API framework
- the migration to said drivers from the the intree drivers
- work for non-cloud provider storage drivers (FC-SAN, iSCSI) being converted to CSI drivers
Background, and strategic fit
In a future Kubernetes release (currently 1.21) intree cloud provider drivers will be deprecated and replaced with CSI equivalents, we need the drivers created so that we continue to support the ecosystems in an appropriate way.
- Storage SIG won't move out the changeover to a later Kubernetes release
Customers will need to be able to use the storage they want.
- Target audience: cluster admins
- Updated content: update storage docs to show how to use these drivers (also better expose the capabilities)