added volumesnapshotclass to helm chart

removed duplicate deletionPolicy

made helm package update

added snapshotclass.yaml in deployer folder

added snapshotclass.yaml in deployer folder

Combined: Removed duplicate deletionPolicy, added snapshotclass.yaml, and updated helm package.

fixed merge conflict

added volumesnapshotclass to helm chart

updated helm value name for volumeSnapshotClass

updated helm value name for volumeSnapshotClass

added volumesnapshotclass to helm chart

format yaml file

added volumesnapshotclass to helm chart

made helm package update

added volumesnapshotclass to helm chart

charts/latest/csi-driver-nfs/templates/snapshotclass.yaml

@@ -0,0 +1,9 @@
+{{- if .Values.volumeSnapshotClass.create }}
+---
+apiVersion: snapshot.storage.k8s.io/v1
+kind: VolumeSnapshotClass
+metadata:
+  name: {{ .Values.volumeSnapshotClass.name }}
+driver: {{ .Values.driver.name }}
+deletionPolicy: {{ .Values.volumeSnapshotClass.deletionPolicy }}
+{{- end }}

charts/latest/csi-driver-nfs/values.yaml

@@ -147,6 +147,7 @@ externalSnapshotter:
   enabled: false
   name: snapshot-controller
   priorityClassName: system-cluster-critical
+  deletionPolicy: Delete
   controller:
     replicas: 1
   resources:
@@ -159,6 +160,12 @@ externalSnapshotter:
   customResourceDefinitions:
     enabled: true   #if set true, VolumeSnapshot, VolumeSnapshotContent and VolumeSnapshotClass CRDs will be created. Set it false, If they already exist in cluster.
 
+## volumeSnapshotClass resource example:
+volumeSnapshotClass:
+  create: false
+  name: csi-nfs-snapclass
+  deletionPolicy: Delete
+  
 ## Reference to one or more secrets to be used when pulling images
 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
 ##

deploy/snapshotclass.yaml

@@ -0,0 +1,7 @@
+---
+apiVersion: snapshot.storage.k8s.io/v1
+kind: VolumeSnapshotClass
+metadata:
+  name: csi-nfs-snapclass
+driver: nfs.csi.k8s.io
+deletionPolicy: Delete