CSI Driver for IBM® Power Systems™ Virtual Servers

The IBM Power Virtual Systems Container Storage Interface (CSI) Driver provides a CSI interface used by Container Orchestrators to manage the lifecycle of Power Virtual System volumes.

The following CSI gRPC calls are implemented:

• Controller Service: CreateVolume, DeleteVolume, ControllerPublishVolume,ControllerUnpublishVolume, ControllerGetCapabilities, ValidateVolumeCapabilities
• Node Service: NodeStageVolume, NodeUnstageVolume, NodePublishVolume, NodeUnpublishVolume, NodeGetCapabilities, NodeGetInfo
• Identity Service: GetPluginInfo, GetPluginCapabilities

There are several optional parameters that could be passed into CreateVolumeRequest.parameters map, these parameters can be configured in StorageClass, see example:

There are couple driver options that can be passed as arguments when starting driver container.

Following sections are Kubernetes specific. If you are Kubernetes user, use followings for driver features, installation steps and examples.

• Static Provisioning - create a new or migrating existing PowerVS volumes, then create persistence volume (PV) from the PowerVS volume and consume the PV from container using persistence volume claim (PVC).
• Dynamic Provisioning - uses persistence volume claim (PVC) to request the Kuberenetes to create the PowerVS volume on behalf of user and consumes the volume from inside container.
• Mount Option - mount options could be specified in persistence volume (PV) to define how the volume should be mounted.
• Volume Resizing - expand the volume size. The corresponding CSI feature (ExpandCSIVolumes) is beta since Kubernetes 1.16.

• If you are managing PowerVS volumes using static provisioning, get yourself familiar with Power Virtual Servers.
• Get yourself familiar with how to setup Kubernetes on IBM Cloud and have a working Kubernetes cluster:
  • Enable flag --allow-privileged=true for kubelet and kube-apiserver
  • Enable kube-apiserver feature gates --feature-gates=CSINodeInfo=true,CSIDriverRegistry=true,CSIBlockVolume=true
  • Enable kubelet feature gates --feature-gates=CSINodeInfo=true,CSIDriverRegistry=true,CSIBlockVolume=true

• Using secret object - Generate IBMCLOUD_APIKEY from the UI, put that user's credentials in secret manifest, then deploy the secret

curl https://raw.githubusercontent.com/kubernetes-sigs/ibm-powervs-block-csi-driver/main/deploy/kubernetes/secret.yaml > secret.yaml
# Edit the IBMCLOUD_API_KEY
# Edit the secret with user credentials
kubectl apply -f secret.yaml

Please see the compatibility matrix above before you deploy the driver

To deploy the CSI driver:

kubectl apply -k "https://github.com/kubernetes-sigs/ibm-powervs-block-csi-driver/deploy/kubernetes/overlays/stable"

Verify driver is running:

kubectl get pods -n kube-system

To view driver debug logs, run the CSI driver with -v=5 command line option

To enable powervs debug logs, run the CSI driver with debug=true command line option.

Make sure you follow the Prerequisites before the examples:

• Dynamic Provisioning
• Block Volume
• Configure StorageClass
• Volume Resizing

Please go through CSI Spec and General CSI driver development guideline to get some basic understanding of CSI driver before you start.

• Golang 1.17.+
• Ginkgo in your PATH for integration testing and end-to-end testing
• Docker 20.10+ for releasing

Dependencies are managed through go module. To build the project, first turn on go mod using export GO111MODULE=on, then build the project using: make

• To create binary, run: make bin/ibm-powervs-block-csi-driver
• To build image, run: make image
• To push image, run: make push