The Zadara VPSA CSI provider implements an interface between the Container Storage Interface (CSI) and Zadara VPSA Storage Array & VPSA All-Flash, for a dynamic provisioning of persistent Block and File volumes.
releasebranch (the default) and tagsrelease-v[version]refer to stable versions.mastercontains the latest changes, some of which may be still not fully tested.
Zadara CSI Driver 2.0 introduces a major change in management of underlying VPSAs and nested resources. Now a single CSI driver supports multiple VPSAs. Check out the Changelog for more details.
All user guides are updated with examples for the new functionality.
🛈 CSI 1.x.y users are required to perform a migration.
A new component, built-in in the CSI Driver deployment.
It introduces a notion of VSC Storage Class: a set of VPSAs used for Volume provisioning.
- VPSAs can be added or removed dynamically.
- VSC decides which VPSA in will be used for Volume provisioning.
Volume Service Controller (VSC) entities are persisted as Kubernetes Custom Resources.
Configuration of CSI driver is done via VSCStorageClass and VPSA Custom Resources (full reference).
VSC: Volume Service Controller: a new component, built-in in the CSI Driver deployment. It aggregates multiple VPSAs and takes Volume scheduling decisions.PVC: Persistent Volume ClaimPV: Persistent VolumeSC: Storage ClassCRD: Custom Resource Definition
- Migration from CSI 1.x.y
- Get the repository
- Prerequisites
- Deploying Zadara CSI Helm Chart. Looking for
helm install? - Quickstart tutorial
Advanced topics:
- Using custom image registry
- Adding custom trusted certificates
- Troubleshooting tips
- Hack scripts to help with management and debugging
- VSC configuration Adding VSC StorageClasses and VPSAs.
- Kubernetes Storage configuration. StorageClasses and PersistentVolumeClaims.
- Extended configuration (ConfigMap)
- Example workload for NAS or Block volumes
- Creating Snapshots and Clones
- Expand Persistent Volume Claim
- Using pre-provisioned Volumes import existing VPSA Volumes into k8s.