@@ -127,7 +127,7 @@ This is `deploy/class.yaml` which defines the NFS subdir external provisioner's
apiVersion:storage.k8s.io/v1
kind:StorageClass
metadata:
name:managed-nfs-storage
name:nfs-client
provisioner:k8s-sigs.io/nfs-subdir-external-provisioner# or choose another name, must match deployment's env PROVISIONER_NAME'
parameters:
pathPattern:"${.PVC.namespace}/${.PVC.annotations.nfs.io/storage-path}"# waits for nfs.io/storage-path annotation, if not specified will accept as empty string.
...
...
@@ -166,7 +166,7 @@ metadata:
annotations:
nfs.io/storage-path:"test-path"# not required, depending on whether this annotation was shown in the storage class description
description:nfs-subdir-external-provisioner is an automatic provisioner that used your *already configured* NFS server, automatically creating Persistent Volumes.
The command deploys the given storage class in the default configuration. It can be used afterswards to provision persistent volumes. The [configuration](#configuration) section lists the parameters that can be configured during installation.
The command deploys the given storage class in the default configuration. It can be used afterwards to provision persistent volumes. The [configuration](#configuration) section lists the parameters that can be configured during installation.
> **Tip**: List all releases using `helm list`
...
...
@@ -84,3 +84,15 @@ The following tables lists the configurable parameters of this chart and their d
| `affinity` | Affinity settings | `{}` |
| `tolerations` | List of node taints to tolerate | `[]` |
| `labels` | Additional labels for any resource created | `{}` |
## Install Multiple Provisioners
It is possible to install more than one provisioner in your cluster to have access to multiple nfs servers and/or multiple exports from a single nfs server. Each provisioner must have a different `storageClass.provisionerName` and a different `storageClass.name`. For example:
