Project reference ↗

If a cluster already has access to an NFS file server, applications still need a convenient way to request their own storage. The NFS client provisioner automated that step by creating directories on the existing share and making them available as Kubernetes persistent volumes. It did not run the file server itself. The project moved to NFS subdir external provisioner, so existing installations need to check naming and deletion behavior when updating the controller.

Current guidance

The upstream NFS client provisioner moved to NFS subdir external provisioner. It uses an existing NFS server.

The repository and image identity changed. Review storage-class names, provisioner identity, mount options and deletion behavior before changing the deployment. A controller move does not necessarily require moving data, but that depends on the existing resource configuration.

Test a new PVC and inspect how a test volume behaves on deletion. Protect production data and check reclaim policies before cleanup. Do not infer that uninstalling a chart preserves every volume or directory.

Historical upstream link check · 2026-10-09

The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.

Source for this check ↗

Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.

The original record

Historical Kubedex content

Original publication: 2018-09-15T10:10:02+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.

NFS-client is an automatic provisioner that use your existing and already configured NFS server to support dynamic provisioning of Kubernetes Persistent Volumes via Persistent Volume Claims. Persistent volumes are provisioned as ${namespace}-${pvcName}-${pvName}.

This chart installs custom storage class into a Kubernetes cluster using the Helm package manager. It also installs an NFS client provisioner into the cluster which dynamically creates persistent volumes from single NFS share.

Prerequisites

  • Kubernetes 1.9+
  • Existing NFS Share

How to deploy nfs-client to your cluster.

To note again, you must already have an NFS Server.

  • Step 1: Get connection information for your NFS server. Make sure your NFS server is accessible from your Kubernetes cluster and get the information you need to connect to it. At a minimum, you will need its hostname.
  • Step 2: Get the NFS-Client Provisioner files. To set up the provisioner you will download a set of YAML files, edit them to add your NFS server’s connection information and then apply each with the kubectl / oc command.

Get all of the files in the deploy directory of this repository. These instructions assume that you have cloned the external-storage repository and have a bash-shell open in the nfs-client directory.

  • Step 3: Setup authorization. If your cluster has RBAC enabled or you are running OpenShift you must authorize the provisioner. If you are in a namespace/project other than “default” edit deploy/rbac.yaml.

Kubernetes:

  • # Set the subject of the RBAC objects to the current namespace where the provisioner is being deployed
  • $ NS=$(kubectl config get-contexts|grep -e “^\*” |awk ‘{print $5}’)
  • $ NAMESPACE=${NS:-default}
  • $ sed -i” “s/namespace:.*/namespace: $NAMESPACE/g” ./deploy/rbac.yaml
  • $ kubectl create -f deploy/rbac.yaml

OpenShift:

On some installations of OpenShift, the default admin user does not have cluster-admin permissions. If these commands fail to refer to the OpenShift documentation for User and Role Management or contact your OpenShift provider to help you grant the right permissions to your admin user.

  • # Set the subject of the RBAC objects to the current namespace where the provisioner is being deployed
  • $ NAMESPACE=oc project -q
  • $ sed -i” “s/namespace:.*/namespace: $NAMESPACE/g” ./deploy/rbac.yaml
  • $ oc create -f deploy/rbac.yaml
  • $ oadm policy add-scc-to-user hostmount-anyuid system:serviceaccount:$NAMESPACE:nfs-client-provisioner

The post Nfs-client-provisioner appeared first on kubedex.com.

Sources & further reading

  1. NFS provisioner migration and chart
  2. Recovered historical source

Spotted something that needs another look?

Help improve this page →