Harvester-CSI-Driver-LVM is derived from metal-stack/csi-driver-lvm.
Harvester-CSI-Driver-LVM utilizes local storage to provide persistent storage for workloads (Usually VM workloads). It will make the VM unable to be migrated to other nodes, but it can provide better performance.
Before you use it, you should have the pre-established Volume Group (VG) on that node. The VG name will be specified in the StorageClass.
The Harvester-CSI-Driver-LVM provides the following features:
- OnDemand Creation of Logical Volume (LV).
- Support LVM type Striped and DM-Thin.
- Support for Raw Block Volume.
- Support Volume Expansion.
- Support Volume Snapshot.
- Support Volume Clone.
NOTE: The Snapshot/Clone feature only works on the same nodes. Clone works for different Volume Groups.
You can use Helm to install the Harvester-CSI-Driver-LVM by remote repo or local helm chart files.
- Install the Harvester-CSI-Driver-LVM locally:
$ git clone https://github.com/harvester/csi-driver-lvm.git
$ cd csi-driver-lvm/deploy
$ helm install harvester-lvm-csi-driver charts/ -n harvester-system
- Install the Harvester-CSI-Driver-LVM by remote repo:
$ helm repo add harvester https://charts.harvesterhci.io
$ helm install harvester/harvester-lvm-csi-driver -n harvester-system
After the installation, you can check the status of the following pods:
$ kubectl get pods -A |grep harvester-csi-driver-lvm
harvester-system harvester-csi-driver-lvm-controller-0 4/4 Running 0 3h2m
harvester-system harvester-csi-driver-lvm-plugin-ctlgp 3/3 Running 1 (14h ago) 14h
harvester-system harvester-csi-driver-lvm-plugin-qxxqs 3/3 Running 1 (14h ago) 14h
harvester-system harvester-csi-driver-lvm-plugin-xktx2 3/3 Running 0 14h
The CSI driver will be installed in the harvester-system namespace and provision to each node.
After installation, you can refer to the examples directory for some example CRDs for usage.
- Implement the unittest
- Implement the webhook for the validation
$ make
The above command will execute the validation and build the target Image.
You can define your REPO and TAG with ENV REPO and TAG.