Connecting Your Kubernetes Cluster to Your Qumulo Cluster by Using the Qumulo Container Storage Interface (CSI) Driver

This section introduces the Qumulo Container Storage Interface (CSI) driver and explains how you can connect your Kubernetes cluster to your Qumulo cluster by using the Qumulo CSI driver.

To automate container storage, enable dynamic volumes, and help you scale your application container images based on usage and workflows, Qumulo uses its CSI driver to connect the Kubernetes orchestrator to Qumulo persistent storage. (In comparison, for example, the NFS CSI Driver for Kubernetes requires unprivileged NFS access for dynamic volumes and doesn’t support volume sizing and expansion.)

For general driver information, see the Container Storage Interface (CSI) Specification.

Supported Features

The Qumulo CSI Driver supports:

Static and dynamic (expansion) provisioning over NFSv3
The following Persistent Volume Claim access modes:
- ReadOnlyMany
- ReadWriteMany
- ReadWriteOnce
- ReadWriteOncePod
NFSv4.1

Important
Even when you enable NFSv4.1 for your Qumulo cluster, you must explicitly configure NFSv4.1 to work with Kerberos.

Unsupported Features

Requirements

A Qumulo cluster
Kubernetes 1.19 (and higher)

Connecting Your Qumulo Cluster to Kubernetes

This section explains how you can configure, provision, and mount Qumulo storage for each Pod (a logical wrapper for a container) on Kubernetes by using dynamic provisioning. This gives you more control over persistent volume capacity.

Step 1: Install the Qumulo CSI Driver

Download the .zip file or use one of the following commands.

S3:

aws s3 cp s3://csi-driver-qumulo/deploy_v1.1.0.zip ./

HTTP:

wget https://csi-driver-qumulo.s3.us-west-2.amazonaws.com/deploy_v1.1.0.zip

Extract the contents of the .zip file.
Run the shell script and specify the current release version. For example:
- Linux:
```
cd deploy_v1.1.0
chmod +x install_driver.sh
./install-driver.sh
```
- Windows:
```
cd deploy_v1.1.0
install-driver.bat
```
The script configures Qumulo’s prebuilt Elastic Container Registry (ECR) image (from public.ecr.aws/qumulo/csi-driver-qumulo:v1.1.0) and installs it on your Kubernetes system.

Step 2: Configure Volume and NFS Export Paths

To prepare your Qumulo cluster for connecting to your Kubernetes cluster, you must first configure your volume and NFS export paths on your Qumulo cluster by setting the following parameters for each storage class that you define.

Tip
Write down the paths for the following YAML keys for the storageclass-qumulo.yaml file that you use when you create a storage class in step 5.

For storeRealPath, from the root of the Qumulo file system, create a directory for storing volumes on your Qumulo cluster, for example /csi/volumes1.

Note
Because the CSI driver doesn’t create the directory listed in the storeRealPath key automatically, this directory must exist below the NFS export and must not be the NFS export itself.
For storeExportPath, create the NFS export for hosting the persistent volume.
If your cluster has more than one tenant, specify the tenant ID that contains your NFS export for the tenantId parameter. For more information, see Configure Multi-Tenancy with Qumulo on Qumulo Care.
Note
- If you have only one tenant, it isn't necessary to specify the `tenantId` parameter.
- You must provide the value for tenantId as a string. For example: "2".

Step 3: Configure Credentials

To connect your Kubernetes cluster to your Qumulo cluster, you must either use an existing account or create a new account for the CSI driver to communicate with the Qumulo API.

Configure a username and password for a user on your Qumulo cluster.
The configured username must have the following file permissions:
- Lookup on storeRealPath
- Create directories in storeRealPath
- Create and modify quotas:
  - PRIVILEGE_QUOTA_READ
  - PRIVILEGE_QUOTA_WRITE
- Read NFS exports: PRIVILEGE_NFS_EXPORT_READ
- Perform TreeDelete operations on volume directories: PRIVILEGE_FS_DELETE_TREE_WRITE

For more information, see Role-Based Access Control (RBAC) with Qumulo Core on Qumulo Care.

Step 4: Create and Configure Secrets

To allow the CSI driver to operate with your Qumulo cluster, you must create and configure Secrets. You may use either Basic Authentication with a username and password, or an Access Token. Depending on configuration, Basic Authentication may be disallowed and using an Access Token will be required.

Configure one of the following authentication types.

Basic Authentication:

kubectl create secret generic cluster1-login \
  --type="kubernetes.io/basic-auth" \
  --from-literal=username=bill \
  --from-literal=password=SuperSecret \
  --namespace=kube-system

Access Token:

TOKEN='access-v1:zNTc5D0zWTdNi/KsZo620fu71TweGh47u+S/5NbV...'
kubectl create secret generic cluster1-login \
  --from-literal=access_token="$TOKEN" \
  --namespace=kube-system

Give the CSI driver access to the Secrets. For example:

kubectl create role access-secrets \
  --verb=get,list,watch \
  --resource=secrets \
  --namespace kube-system
kubectl create rolebinding \
  --role=access-secrets default-to-secrets \
  --serviceaccount=kube-system:csi-qumulo-controller-sa \
  --namespace kube-system

Step 5: Create a Storage Class

To link your Kubernetes cluster to your Qumulo cluster, you must create a storage class on your Kubernetes cluster.

Begin with the example Qumulo storage class configuration.

Note

In the following example, it is possible to use a fully qualified domain name (FQDN) for the parameters: server: entry.
For such a configuration, all Kubernetes nodes in the cluster must be able to resolve FQDNs.

---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cluster1
provisioner: qumulo.csi.k8s.io
parameters:
  server: 203.0.113.0
  storeRealPath: "/regions/4234/volumes"
  storeExportPath: "/some/export"
  csi.storage.k8s.io/provisioner-secret-name: cluster1-login
  csi.storage.k8s.io/provisioner-secret-namespace: kube-system
  csi.storage.k8s.io/controller-expand-secret-name: cluster1-login
  csi.storage.k8s.io/controller-expand-secret-namespace: kube-system
reclaimPolicy: Delete
volumeBindingMode: Immediate
mountOptions:
  - nolock
  - proto=tcp
  - vers=3
allowVolumeExpansion: true

Edit the configuration for your Qumulo cluster.
1. Name your storage class.
2. Specify server and storeRealPath.
3. Specify storeExportPath.
4. (Optional) Specify tenantId.
  
  Note
  You must provide the value for tenantId as a string. For example: "2".
5. Configure the following parameters to point to the Secrets that you have created and configured in the namespace in which you installed the CSI driver:
  - controller-expand-secret-name
  - controller-expand-secret-namespace
  - provisioner-secret-name
  - provisioner-secret-namespace
6. Specify the NFS mountOptions. For example:
```
mountOptions:
  - nolock
  - proto=tcp
  - vers=3
```
7. To create the class, apply the configuration. For example:
```
kubectl create -f storageclass-qumulo.yaml
```

Step 6: Create a Persistent Volume Claim (PVC) and Apply it to a Pod

To apply a PVC claim to a Pod dynamically, you must first configure and create it.

Begin with the example PVC configuration.

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: claim1
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: cluster1
  resources:
    requests:
      storage: 1Gi

Edit the configuration for your PVC claim.
1. Name your claim.
2. Change storeClassName to the name of your claim.
3. Specify the capacity in spec.resources.requests.storage. This parameter lets you create a quota on your Qumulo cluster.
4. To create the claim, apply the configuration. For example:
```
kubectl apply -f dynamic-pvc.yaml
```

Use the claim in a Pod or a Deployment. For example:

---
apiVersion: v1
kind: Pod
metadata:
  name: claim1-pod
spec:
  volumes:
    - name: cluster1
      persistentVolumeClaim:
        claimName: claim1
  containers:
    - name: claim1-container
      image: ...
      volumeMounts:
        - mountPath: "/cluster1"
          name: cluster1

Important
When the PVC is released, a tree-delete is initiated on the Qumulo cluster for the directory that the PVC indicates. To prevent this behavior, set reclaimPolicy to Retain.

You can launch and use your container image.