add leader election for dashboard

Signed-off-by: zwwhdls <zww@hdls.me>

charts/juicefs-csi-driver/templates/deployment.yaml

@@ -8,7 +8,7 @@ metadata:
   name: juicefs-csi-dashboard
   namespace: {{ .Release.Namespace | quote }}
 spec:
-  replicas: 1
+  replicas: {{ .Values.dashboard.replicas }}
   selector:
     matchLabels:
       app: juicefs-csi-dashboard
@@ -32,6 +32,15 @@ spec:
           {{- end }}
           args:
            - --static-dir=/dist
+          {{- if .Values.dashboard.leaderElection.enabled }}
+          - --leader-election
+          {{- if .Values.dashboard.leaderElection.leaderElectionNamespace }}
+          - --leader-election-namespace={{ .Values.dashboard.leaderElection.leaderElectionNamespace }}
+          {{- end }}
+          {{- if .Values.dashboard.leaderElection.leaseDuration }}
+          - --leader-election-lease-duration={{ .Values.dashboard.leaderElection.leaseDuration }}
+          {{- end }}
+          {{- end }}
           env:
             - name: SYS_NAMESPACE
               valueFrom:

charts/juicefs-csi-driver/values.yaml

@@ -178,6 +178,16 @@ node:
 dashboard:
   # CSI Dashboard helps with CSI Driver observation, disabled by default
   enabled: false
+  replicas: 2
+  leaderElection:
+    # Enable leader election for dashboard.
+    enabled: true
+    # The namespace where the leader election resource lives. Defaults to the pod namespace if not set
+    leaderElectionNamespace: ""
+    # The duration that non-leader candidates will wait to force acquire leadership. This is measured against time of last observed ack
+    # Defaults to 15s, if not set
+    leaseDuration: ""
+    # The duration that the acting control-plane will retry refreshing leadership before giving up
   hostNetwork: false
   resources:
     limits: