Filesystem PVC and POD Workload

This chart will install the following resources:

A PVC named example-fs-pvc referencing the previously defined StorageClass.
A POD named example-fs-pod using example-fs-pvc.

Deploying the Filesystem Workload

Bash
    
 
helm install \  --set filesystem.enabled=true \  lb-csi-workload-filesystem \  lightbits-helm-repo/lb-csi-workload-examples
Copy

Will output:

Bash
    
 
NAME: lb-csi-workload-filesystemLAST DEPLOYED: Sun Feb 21 16:09:02 2021NAMESPACE: defaultSTATUS: deployedREVISION: 1TEST SUITE: None
Copy

Deploying the POD on a Specific K8S Node

You can choose to deploy the POD on a specific K8s node by specifying nodeName or nodeSelector in the template.

The default values for these parameters are empty, which means the POD will not be limited to any POD.

Examples:

Specifying nodeSelector:

Bash
    
 
helm template \--set filesystem.enabled=true \--set filesystem.nodeSelector."beta\.kubernetes\.io/arch"=amd64,filesystem.nodeSelector.disktype=ssd \lightbits-helm-repo/lb-csi-workload-examples
Copy

Will result in:

Bash
    
 
kind: PodapiVersion: v1metadata:name: example-filesystem-podspec:nodeSelector:beta.kubernetes.io/arch: amd64disktype: ssdcontainers:...
Copy

Specifying nodeName:

Bash
    
 
helm template \--set filesystem.enabled=true \--set filesystem.nodeName=node00.local \lightbits-helm-repo/lb-csi-workload-examples
Copy

Will result in:

Bash
    
 
kind: PodapiVersion: v1metadata:name: example-fs-podspec:nodeName: node00.localcontainers:...
Copy

Verifying the Filesystem Workload Deployed

Verify that PV, PVC are created and in Bounded state, and that POD is in Running state:

Bash
    
​x
    
kubectl get pv,pvc,podsNAME                                                        CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                    STORAGECLASS   REASON   AGEpersistentvolume/pvc-e0ad4f63-4b42-417f-8bed-94f8aec8f0d5   10Gi       RWO            Delete           Bound    default/example-fs-pvc   example-sc              33s​NAME                                   STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGEpersistentvolumeclaim/example-fs-pvc   Bound    pvc-e0ad4f63-4b42-417f-8bed-94f8aec8f0d5   10Gi       RWO            example-sc     34s​NAME                 READY   STATUS    RESTARTS   AGEpod/example-fs-pod   1/1     Running   0          34s
Copy

Uninstalling the Filesystem Workload

Bash
    
 
helm uninstall lb-csi-workload-filesystem
Copy

Verify that all resources are gone:

Bash
    
 
kubectl get pv,pvc,podsNo resources found in default namespace.
Copy

Last updated on

Was this page helpful?