add accessModes (#38)

This commit is contained in:
Simon Smith 2020-11-15 20:41:16 +00:00 committed by GitHub
parent a36a6852cf
commit 463abed9a0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 37 additions and 33 deletions

View File

@ -1,7 +1,7 @@
apiVersion: v1
description: nfs-client is an automatic provisioner that used your *already configured* NFS server, automatically creating Persistent Volumes.
name: nfs-client-provisioner
version: 1.0.1
version: 1.0.2
appVersion: 3.1.0
home: https://github.com/kubernetes-incubator/external-storage/tree/master/nfs-client
sources:

View File

@ -1,6 +1,6 @@
# nfs-client-provisioner
The [NFS client provisioner](https://github.com/kubernetes-incubator/external-storage/tree/master/nfs-client) is an automatic provisioner for Kubernetes that uses your *already configured* NFS server, automatically creating Persistent Volumes.
The [NFS client provisioner](https://github.com/kubernetes-incubator/external-storage/tree/master/nfs-client) is an automatic provisioner for Kubernetes that uses your _already configured_ NFS server, automatically creating Persistent Volumes.
## TL;DR;
@ -46,7 +46,7 @@ The command removes all the Kubernetes components associated with the chart and
The following tables lists the configurable parameters of this chart and their default values.
| Parameter | Description | Default |
| --------------------------------- | ------------------------------------- | --------------------------------------------------------- |
| ----------------------------------- | ----------------------------------------------------------- | ------------------------------------------------- |
| `replicaCount` | Number of provisioner instances to deployed | `1` |
| `strategyType` | Specifies the strategy used to replace old Pods by new ones | `Recreate` |
| `image.repository` | Provisioner image | `quay.io/external_storage/nfs-client-provisioner` |
@ -58,6 +58,7 @@ The following tables lists the configurable parameters of this chart and their d
| `storageClass.reclaimPolicy` | Method used to reclaim an obsoleted volume | `Delete` |
| `storageClass.provisionerName` | Name of the provisionerName | null |
| `storageClass.archiveOnDelete` | Archive pvc when deleting | `true` |
| `storageClass.accessModes` | Set access mode for PV | `ReadWriteOnce` |
| `nfs.server` | Hostname of the NFS server | null (ip or hostname) |
| `nfs.path` | Basepath of the mount point to be used | `/ifs/kubernetes` |
| `nfs.mountOptions` | Mount options (e.g. 'nfsvers=3') | null |
@ -70,4 +71,3 @@ The following tables lists the configurable parameters of this chart and their d
| `nodeSelector` | Node labels for pod assignment | `{}` |
| `affinity` | Affinity settings | `{}` |
| `tolerations` | List of node taints to tolerate | `[]` |

View File

@ -10,7 +10,7 @@ spec:
storage: 10Mi
volumeMode: Filesystem
accessModes:
- ReadWriteOnce
- {{ .Values.storageClass.accessModes }}
persistentVolumeReclaimPolicy: {{ .Values.storageClass.reclaimPolicy }}
storageClassName: ""
{{- if .Values.nfs.mountOptions }}

View File

@ -5,7 +5,7 @@ metadata:
name: pvc-{{ template "nfs-client-provisioner.fullname" . }}
spec:
accessModes:
- ReadWriteOnce
- {{ .Values.storageClass.accessModes }}
volumeMode: Filesystem
storageClassName: ""
selector:

View File

@ -39,6 +39,9 @@ storageClass:
# When set to false your PVs will not be archived by the provisioner upon deletion of the PVC.
archiveOnDelete: true
# Set access mode - ReadWriteOnce, ReadOnlyMany or ReadWriteMany
accessModes: ReadWriteOnce
## For RBAC support:
rbac:
# Specifies whether RBAC resources should be created
@ -60,7 +63,8 @@ serviceAccount:
# If not set and create is true, a name is generated using the fullname template
name:
resources: {}
resources:
{}
# limits:
# cpu: 100m
# memory: 128Mi