The Container Storage Interface (CSI) is the new model for integrating storage system service with Kubernetes and other orchestration systems. Kubernetes has had support for CSI since 1.10 as beta.
With CSI, Kubernetes gives storage drivers the opportunity to release on their schedule. This allows storage vendors to upgrade, update, and enhance their drivers without the need to update Kubernetes, maintaining a consistent, dependable, orchestration system.
Note, that currently this deployment mode is available only as a Tech Preview for Release 1.4.
Install using the Portworx spec generator
When installing Portworx through install.portworx.com you can select CSI as the model to use for deployment (see “Customize” tab, “Advanced Settings” and “Enable CSI”).
If you are using curl to fetch the Portworx spec, you can add
csi=true to the parameter list to include CSI specs in the generated file.
Impact on applications
The only affected object is the StorageClass. For any StorageClasses created, you will need to setup the value of
com.openstorage.pxd. Here is an example:
kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: portworx provisioner: com.openstorage.pxd parameters: repl: "3"
Your PersistentVolumes and PersistentVolumeClaims will all work the same as before.
Currently upgrades are not supported. You will need to deploy using CSI onto a new Kubernetes cluster. The Kubernetes community is working very hard to make this possible in the near future.
Portworx welcomes contributions to our CSI implemenation, which is open-source and repository is at OpenStorage.