4.2 KiB

Installation with Helm 3

Follow this guide to install the NFS Driver for Kubernetes.

Prerequisites

Install via helm install

$ cd charts/latest
$ helm install csi-driver-nfs ./csi-driver-nfs -n kube-system

Install via Helm repository

$ helm repo add csi-driver-nfs https://raw.githubusercontent.com/kubernetes-csi/csi-driver-nfs/master/charts
$ helm install --name csi-driver-nfs csi-driver-nfs/csi-driver-nfs --namespace kube-system

Search for available versions

$ helm search repo -l csi-driver-nfs

Install a specific version

https://raw.githubusercontent.com/kubernetes-csi/csi-driver-nfs/master/charts --version v2.0.0

Chart configuration

The following table lists the configurable parameters of the latest NFS CSI Driver chart and their default values.

Parameter Description Default
image.nfs.repository csi-driver-nfs docker image gcr.io/k8s-staging-sig-storage/nfsplugin
image.nfs.tag csi-driver-nfs docker image tag amd64-linux-canary
image.nfs.pullPolicy csi-driver-nfs image pull policy IfNotPresent
image.csiProvisioner.repository csi-provisioner docker image k8s.gcr.io/sig-storage/csi-provisioner
image.csiProvisioner.tag csi-provisioner docker image tag v2.0.4
image.csiProvisioner.pullPolicy csi-provisioner image pull policy IfNotPresent
image.livenessProbe.repository liveness-probe docker image k8s.gcr.io/sig-storage/livenessprobe
image.livenessProbe.tag liveness-probe docker image tag v2.1.0
image.livenessProbe.pullPolicy liveness-probe image pull policy IfNotPresent
image.nodeDriverRegistrar.repository csi-node-driver-registrar docker image k8s.gcr.io/sig-storage/csi-node-driver-registrar
image.nodeDriverRegistrar.tag csi-node-driver-registrar docker image tag v2.0.1
image.nodeDriverRegistrar.pullPolicy csi-node-driver-registrar image pull policy IfNotPresent
serviceAccount.create whether create service account of csi-nfs-controller true
rbac.create whether create rbac of csi-nfs-controller true
controller.replicas the replicas of csi-nfs-controller 2

Troubleshooting

If there are some errors when using helm to install, follow the steps to debug:

  1. Add --wait -v=5 --debug in helm install command.
  2. Then the error pods can be located.
  3. Use kubectl describe to acquire more info.
  4. Check the related resource of the pod, such as serviceaacount, rbac, etc.