set priorityclass on provisioner pods

set system-cluster-critical priorityclass on
provisioner pods. the system-cluster-critical is
having lowest priority compared to node-critical.

Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>

charts/ceph-csi-cephfs/templates/provisioner-deployment.yaml

@@ -42,6 +42,9 @@ spec:
               topologyKey: "kubernetes.io/hostname"
 {{- end }}
       serviceAccountName: {{ include "ceph-csi-cephfs.serviceAccountName.provisioner" . }}
+{{- if .Values.provisioner.priorityClassName }}
+      priorityClassName: {{ .Values.provisioner.priorityClassName }}
+{{- end }}
       containers:
         - name: csi-provisioner
           image: "{{ .Values.provisioner.provisioner.image.repository }}:{{ .Values.provisioner.provisioner.image.tag }}"

charts/ceph-csi-cephfs/values.yaml

@@ -39,6 +39,10 @@ nodeplugin:
   # if you are using ceph-fuse client set this value to OnDelete
   updateStrategy: RollingUpdate
 
+  # set user created priorityclassName for csi plugin pods. default is
+  # system-node-critical which is highest priority
+  priorityClassName: system-node-critical
+
   httpMetrics:
     # Metrics only available for cephcsi/cephcsi => 1.2.0
     # Specifies whether http metrics should be exposed
@@ -105,6 +109,10 @@ provisioner:
   # Timeout for waiting for creation or deletion of a volume
   timeout: 60s
 
+  # set user created priorityclassName for csi provisioner pods. default is
+  # system-cluster-critical which is less priority than system-node-critical
+  priorityClassName: system-cluster-critical
+
   httpMetrics:
     # Metrics only available for cephcsi/cephcsi => 1.2.0
     # Specifies whether http metrics should be exposed