fix: helm upgrade failed with pvc.enabled

Helm upgrade failed with pvc.enabled but without pvc.storageClassName
related to Issue: #667

Author: DmitriyStoyanov

snyk-monitor/templates/pvc.yaml

@@ -13,5 +13,11 @@ spec:
   resources:
     requests:
       storage: {{ .Values.temporaryStorageSize }}
-  storageClassName: {{ .Values.pvc.storageClassName }}
+  {{- if .Values.pvc.storageClassName }}
+  {{- if (eq "-" .Values.pvc.storageClassName) }}
+  storageClassName: ""
+  {{- else }}
+  storageClassName: "{{ .Values.pvc.storageClassName }}"
+  {{- end }}
+  {{- end }}
 {{- end }}{{- end }}

snyk-monitor/values.yaml

@@ -40,7 +40,14 @@ temporaryStorageSize: 50Gi #  Applies to PVC too
 pvc:
   enabled: false
   name: snyk-monitor-pvc
-  storageClassName: null
+  ## snyk-monitor data Persistent Volume Storage Class
+  ## If defined, storageClassName: <storageClass>
+  ## If set to "-", storageClassName: "", which disables dynamic provisioning
+  ## If undefined (the default) or set to null, no storageClassName spec is
+  ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
+  ##   GKE, AWS & OpenStack)
+  ##
+  # storageClassName: "-"
 
 # Node.js in-container process memory enhancements
 envs: