Kubernetes: Dynamic NFS-Client Provisioner

If you have already setup your NFS server, you can use Dynamic NFS-Client Provisioner , to automatically provision Persistent Volume when you deploy your Persistent Volume Claim. In other words, you don’t have to create your

The easiest way to install it is using Helm.

helm install stable/nfs-client-provisioner --set nfs.server=<nfs-server-ip-address> --set nfs.path=<nfs-server-sharedfolder-path>

One hiccup that I faced is the command above return:

Error: no available release name found

The solution:

kubectl create serviceaccount --namespace kube-system tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'

Now you can test it out, by creating PVC. We expect the PV will be automatically dynamically created.

testpvc.yaml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
 name: test-claim
 annotations:
 volume.beta.kubernetes.io/storage-class: “nfs-client”
spec:
 accessModes:
 — ReadWriteMany
 resources:
 requests:
 storage: 1Mi

Create the PVC:

kubectl create -f testpvc.yaml

test-claim PVC succesfully created

PV is dynamically created when you create PVC

That’s all folks!