fix: refine deployment config to support sel setup k8s cluster

fix yaml lint

Author: andyzhangx

charts/latest/blob-csi-driver-v1.6.0.tgz

@@ -129,9 +129,6 @@ spec:
               name: socket-dir
             - mountPath: /etc/kubernetes/
               name: azure-cred
-            - mountPath: /var/lib/waagent/ManagedIdentity-Settings
-              readOnly: true
-              name: msi
             {{- if eq .Values.cloud "AzureStackCloud" }}
             - name: ssl
               mountPath: /etc/ssl/certs
@@ -171,10 +168,7 @@ spec:
         - name: azure-cred
           hostPath:
             path: /etc/kubernetes/
-            type: Directory
-        - name: msi
-          hostPath:
-            path: /var/lib/waagent/ManagedIdentity-Settings
+            type: DirectoryOrCreate
         {{- if eq .Values.cloud "AzureStackCloud" }}
         - name: ssl
           hostPath:

charts/latest/blob-csi-driver/templates/csi-blob-controller.yaml

@@ -156,9 +156,6 @@ spec:
               name: mountpoint-dir
             - mountPath: /etc/kubernetes/
               name: azure-cred
-            - mountPath: /var/lib/waagent/ManagedIdentity-Settings
-              readOnly: true
-              name: msi
             - mountPath: /mnt
               name: blob-cache
             {{- if eq .Values.cloud "AzureStackCloud" }}
@@ -190,11 +187,8 @@ spec:
           name: registration-dir
         - hostPath:
             path: /etc/kubernetes/
-            type: Directory
+            type: DirectoryOrCreate
           name: azure-cred
-        - hostPath:
-            path: /var/lib/waagent/ManagedIdentity-Settings
-          name: msi
         - hostPath:
             path: {{ .Values.node.blobfuseCachePath }}
           name: blob-cache

charts/latest/blob-csi-driver/templates/csi-blob-node.yaml

@@ -101,9 +101,6 @@ spec:
               name: socket-dir
             - mountPath: /etc/kubernetes/
               name: azure-cred
-            - mountPath: /var/lib/waagent/ManagedIdentity-Settings
-              readOnly: true
-              name: msi
           resources:
             limits:
               cpu: 200m
@@ -137,7 +134,4 @@ spec:
         - name: azure-cred
           hostPath:
             path: /etc/kubernetes/
-            type: Directory
-        - name: msi
-          hostPath:
-            path: /var/lib/waagent/ManagedIdentity-Settings
+            type: DirectoryOrCreate

deploy/csi-blob-controller.yaml

@@ -128,9 +128,6 @@ spec:
               name: mountpoint-dir
             - mountPath: /etc/kubernetes/
               name: azure-cred
-            - mountPath: /var/lib/waagent/ManagedIdentity-Settings
-              readOnly: true
-              name: msi
             - mountPath: /mnt
               name: blob-cache
           resources:
@@ -155,12 +152,10 @@ spec:
           name: registration-dir
         - hostPath:
             path: /etc/kubernetes/
-            type: Directory
+            type: DirectoryOrCreate
           name: azure-cred
-        - hostPath:
-            path: /var/lib/waagent/ManagedIdentity-Settings
-          name: msi
         - hostPath:
             path: /mnt
+            type: DirectoryOrCreate
           name: blob-cache
 ---

deploy/csi-blob-node.yaml

@@ -19,3 +19,4 @@ mountOptions:
   - -o attr_timeout=120
   - -o entry_timeout=120
   - -o negative_timeout=120
+  - --cache-size-mb=1000  # Default will be 80% of available memory, eviction will happen beyond that.

deploy/example/storageclass-blobfuse-existing-container.yaml

@@ -15,4 +15,4 @@ mountOptions:
   - -o allow_other
   - --file-cache-timeout-in-seconds=0
   - --cancel-list-on-mount-seconds=60  # prevent billing charges on mounting
-  - --log-level=LOG_DEBUG  # only for debugging
+  - --log-level=LOG_DEBUG  # LOG_WARNING, LOG_INFO, LOG_DEBUG

deploy/example/storageclass-blobfuse-readonly.yaml

@@ -16,3 +16,5 @@ mountOptions:
   - -o attr_timeout=120
   - -o entry_timeout=120
   - -o negative_timeout=120
+  - --log-level=LOG_WARNING  # LOG_WARNING, LOG_INFO, LOG_DEBUG
+  - --cache-size-mb=1000  # Default will be 80% of available memory, eviction will happen beyond that.