How to migrate the FlexVolume storage plugin - Container Service for Kubernetes

Le plug-in FlexVolume est obsolète et n'est plus pris en charge dans les nouveaux clusters Container Service for Kubernetes (ACK). Migrez vos volumes persistants (PV) et vos revendications de volume persistant (PVC) File Storage NAS (NAS) pré-provisionnés statiquement de FlexVolume vers Container Storage Interface (CSI) afin de maintenir la prise en charge du plug-in et d'accéder aux nouvelles fonctionnalités de stockage.

Si votre cluster contient également des volumes de disque gérés par FlexVolume, utilisez plutôt le contrôleur csi-compatible-controller.

Impacts

Les PVC sont recréés pendant la migration, ce qui entraîne le redémarrage des pods.
Les redémarrages de pod interrompent les charges de travail en cours d'exécution. Effectuez la migration pendant les heures creuses.

Comparaison entre FlexVolume et CSI

Attribut	CSI	FlexVolume
Composants	CSI-Provisioner (Deployment) : création automatique de volumes, création de snapshots, stockage CNFS, restauration des données après suppression accidentelle. CSI-Plugin (DaemonSet) : montage et démontage automatiques des volumes. Prend en charge par défaut les volumes de disque, NAS et OSS.	Disk-Controller (Deployment) : création automatique de volumes. FlexVolume (DaemonSet) : montage et démontage des volumes. Prend en charge par défaut les volumes de disque, NAS et OSS.
Paramètre kubelet	Le paramètre `enable-controller-attach-detach` doit être défini sur `true` sur chaque nœud.	Le paramètre `enable-controller-attach-detach` doit être défini sur `true` sur chaque nœud.
Références	Stockage	Présentation de FlexVolume

Prérequis

Installez le plug-in CSI dans votre cluster avant de commencer.

Créez des fichiers nommés csi-plugin.yaml et csi-provisioner.yaml.

Afficher le fichier csi-plugin.yaml

   ---
   apiVersion: v1
   kind: ServiceAccount
   metadata:
     name: csi-admin
     namespace: kube-system
   ---
   kind: ClusterRole
   apiVersion: rbac.authorization.k8s.io/v1
   metadata:
     name: alicloud-csi-plugin
   rules:
     - apiGroups: [""]
       resources: ["secrets"]
       verbs: ["get", "create", "list"]
     - apiGroups: [""]
       resources: ["persistentvolumes"]
       verbs: ["get", "list", "watch", "update", "create", "delete", "patch"]
     - apiGroups: [""]
       resources: ["persistentvolumeclaims"]
       verbs: ["get", "list", "watch", "update"]
     - apiGroups: [""]
       resources: ["persistentvolumeclaims/status"]
       verbs: ["get", "list", "watch", "update", "patch"]
     - apiGroups: ["storage.k8s.io"]
       resources: ["storageclasses"]
       verbs: ["get", "list", "watch"]
     - apiGroups: ["storage.k8s.io"]
       resources: ["csinodes"]
       verbs: ["get", "list", "watch"]
     - apiGroups: [""]
       resources: ["events"]
       verbs: ["get", "list", "watch", "create", "update", "patch"]
     - apiGroups: [""]
       resources: ["endpoints"]
       verbs: ["get", "watch", "list", "delete", "update", "create"]
     - apiGroups: [""]
       resources: ["configmaps"]
       verbs: ["get", "watch", "list", "delete", "update", "create"]
     - apiGroups: [""]
       resources: ["nodes"]
       verbs: ["get", "list", "watch", "update"]
     - apiGroups: ["csi.storage.k8s.io"]
       resources: ["csinodeinfos"]
       verbs: ["get", "list", "watch"]
     - apiGroups: ["storage.k8s.io"]
       resources: ["volumeattachments"]
       verbs: ["get", "list", "watch", "update", "patch"]
     - apiGroups: ["snapshot.storage.k8s.io"]
       resources: ["volumesnapshotclasses"]
       verbs: ["get", "list", "watch", "create"]
     - apiGroups: ["snapshot.storage.k8s.io"]
       resources: ["volumesnapshotcontents"]
       verbs: ["create", "get", "list", "watch", "update", "delete"]
     - apiGroups: ["snapshot.storage.k8s.io"]
       resources: ["volumesnapshots"]
       verbs: ["get", "list", "watch", "update", "create"]
     - apiGroups: ["apiextensions.k8s.io"]
       resources: ["customresourcedefinitions"]
       verbs: ["create", "list", "watch", "delete", "get", "update", "patch"]
     - apiGroups: ["coordination.k8s.io"]
       resources: ["leases"]
       verbs: ["get", "create", "list", "watch", "delete", "update"]
     - apiGroups: ["snapshot.storage.k8s.io"]
       resources: ["volumesnapshotcontents/status"]
       verbs: ["update"]
     - apiGroups: ["storage.k8s.io"]
       resources: ["volumeattachments/status"]
       verbs: ["patch"]
     - apiGroups: ["snapshot.storage.k8s.io"]
       resources: ["volumesnapshots/status"]
       verbs: ["update"]
     - apiGroups: ["storage.k8s.io"]
       resources: ["storageclasses"]
       verbs: ["get", "list", "watch"]
     - apiGroups: [""]
       resources: ["namespaces"]
       verbs: ["get", "list"]
     - apiGroups: [""]
       resources: ["pods","pods/exec"]
       verbs: ["create", "delete", "get", "post", "list", "watch", "patch", "update"]
     - apiGroups: ["storage.alibabacloud.com"]
       resources: ["rules"]
       verbs: ["get"]
     - apiGroups: ["storage.alibabacloud.com"]
       resources: ["containernetworkfilesystems"]
       verbs: ["get","list", "watch"]
   ---
   kind: ClusterRoleBinding
   apiVersion: rbac.authorization.k8s.io/v1
   metadata:
     name: alicloud-csi-plugin
   subjects:
     - kind: ServiceAccount
       name: csi-admin
       namespace: kube-system
   roleRef:
     kind: ClusterRole
     name: alicloud-csi-plugin
     apiGroup: rbac.authorization.k8s.io
   ---
   apiVersion: storage.k8s.io/v1
   kind: CSIDriver
   metadata:
     name: diskplugin.csi.alibabacloud.com
   spec:
     attachRequired: true
     podInfoOnMount: true
   ---
   apiVersion: storage.k8s.io/v1
   kind: CSIDriver
   metadata:
     name: nasplugin.csi.alibabacloud.com
   spec:
     attachRequired: false
     podInfoOnMount: true
   ---
   apiVersion: storage.k8s.io/v1
   kind: CSIDriver
   metadata:
     name: ossplugin.csi.alibabacloud.com
   spec:
     attachRequired: false
     podInfoOnMount: true
   ---
   kind: DaemonSet
   apiVersion: apps/v1
   metadata:
     name: csi-plugin
     namespace: kube-system
   spec:
     selector:
       matchLabels:
         app: csi-plugin
     template:
       metadata:
         labels:
           app: csi-plugin
       spec:
         tolerations:
           - operator: Exists
         affinity:
           nodeAffinity:
             requiredDuringSchedulingIgnoredDuringExecution:
               nodeSelectorTerms:
               - matchExpressions:
                 - key: type
                   operator: NotIn
                   values:
                   - virtual-kubelet
         nodeSelector:
           kubernetes.io/os: linux
         serviceAccount: csi-admin
         priorityClassName: system-node-critical
         hostNetwork: true
         hostPID: true
         dnsPolicy: ClusterFirst
         containers:
           - name: disk-driver-registrar
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-node-driver-registrar:v2.3.1-038aeb6-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             args:
               - "--v=5"
               - "--csi-address=/var/lib/kubelet/csi-plugins/diskplugin.csi.alibabacloud.com/csi.sock"
               - "--kubelet-registration-path=/var/lib/kubelet/csi-plugins/diskplugin.csi.alibabacloud.com/csi.sock"
             volumeMounts:
               - name: kubelet-dir
                 mountPath: /var/lib/kubelet
               - name: registration-dir
                 mountPath: /registration
           - name: nas-driver-registrar
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-node-driver-registrar:v2.3.1-038aeb6-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             args:
               - "--v=5"
               - "--csi-address=/var/lib/kubelet/csi-plugins/nasplugin.csi.alibabacloud.com/csi.sock"
               - "--kubelet-registration-path=/var/lib/kubelet/csi-plugins/nasplugin.csi.alibabacloud.com/csi.sock"
             volumeMounts:
               - name: kubelet-dir
                 mountPath: /var/lib/kubelet/
               - name: registration-dir
                 mountPath: /registration
           - name: oss-driver-registrar
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-node-driver-registrar:v2.3.1-038aeb6-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             args:
               - "--v=5"
               - "--csi-address=/var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock"
               - "--kubelet-registration-path=/var/lib/kubelet/csi-plugins/ossplugin.csi.alibabacloud.com/csi.sock"
             volumeMounts:
               - name: kubelet-dir
                 mountPath: /var/lib/kubelet/
               - name: registration-dir
                 mountPath: /registration
           - name: csi-plugin
             securityContext:
               privileged: true
               allowPrivilegeEscalation: true
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-plugin:v1.24.6-55c95dd-aliyun
             args:
               - "--endpoint=$(CSI_ENDPOINT)"
               - "--v=2"
               - "--driver=oss,nas,disk"
             env:
               - name: KUBE_NODE_NAME
                 valueFrom:
                   fieldRef:
                     apiVersion: v1
                     fieldPath: spec.nodeName
               - name: CSI_ENDPOINT
                 value: unix://var/lib/kubelet/csi-plugins/driverplugin.csi.alibabacloud.com-replace/csi.sock
               - name: MAX_VOLUMES_PERNODE
                 value: "15"
               - name: SERVICE_TYPE
                 value: "plugin"
             resources:
               requests:
                 cpu: 100m
                 memory: 128Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             livenessProbe:
               httpGet:
                 path: /healthz
                 port: healthz
                 scheme: HTTP
               initialDelaySeconds: 10
               periodSeconds: 30
               timeoutSeconds: 5
               failureThreshold: 5
             readinessProbe:
               httpGet:
                 path: /healthz
                 port: healthz
               initialDelaySeconds: 10
               periodSeconds: 30
               timeoutSeconds: 5
               failureThreshold: 5
             ports:
               - name: healthz
                 containerPort: 11260
             volumeMounts:
               - name: kubelet-dir
                 mountPath: /var/lib/kubelet/
                 mountPropagation: "Bidirectional"
               - name: etc
                 mountPath: /host/etc
               - name: host-log
                 mountPath: /var/log/
               - name: ossconnectordir
                 mountPath: /host/usr/
               - name: container-dir
                 mountPath: /var/lib/container
                 mountPropagation: "Bidirectional"
               - name: host-dev
                 mountPath: /dev
                 mountPropagation: "HostToContainer"
               - mountPath: /var/addon
                 name: addon-token
                 readOnly: true
               - mountPath: /host/var/run/
                 name: fuse-metrics-dir
         volumes:
           - name: fuse-metrics-dir
             hostPath:
               path: /var/run/
               type: DirectoryOrCreate
           - name: registration-dir
             hostPath:
               path: /var/lib/kubelet/plugins_registry
               type: DirectoryOrCreate
           - name: container-dir
             hostPath:
               path: /var/lib/container
               type: DirectoryOrCreate
           - name: kubelet-dir
             hostPath:
               path: /var/lib/kubelet
               type: Directory
           - name: host-dev
             hostPath:
               path: /dev
           - name: host-log
             hostPath:
               path: /var/log/
           - name: etc
             hostPath:
               path: /etc
           - name: ossconnectordir
             hostPath:
               path: /usr/
           - name: addon-token
             secret:
               defaultMode: 420
               optional: true
               items:
               - key: addon.token.config
                 path: token-config
               secretName: addon.csi.token
     updateStrategy:
       rollingUpdate:
         maxUnavailable: 30%
       type: RollingUpdate

Afficher le fichier csi-provisioner.yaml

   ---
   kind: Deployment
   apiVersion: apps/v1
   metadata:
     name: csi-provisioner
     namespace: kube-system
   spec:
     selector:
       matchLabels:
         app: csi-provisioner
     strategy:
       rollingUpdate:
         maxSurge: 0
         maxUnavailable: 1
       type: RollingUpdate
     replicas: 2
     template:
       metadata:
         labels:
           app: csi-provisioner
       spec:
         affinity:
           nodeAffinity:
             preferredDuringSchedulingIgnoredDuringExecution:
             - weight: 1
               preference:
                 matchExpressions:
                 - key: node-role.kubernetes.io/master
                   operator: Exists
             requiredDuringSchedulingIgnoredDuringExecution:
               nodeSelectorTerms:
               - matchExpressions:
                 - key: type
                   operator: NotIn
                   values:
                   - virtual-kubelet
           podAntiAffinity:
             preferredDuringSchedulingIgnoredDuringExecution:
             - weight: 100
               podAffinityTerm:
                 labelSelector:
                   matchExpressions:
                   - key: app
                     operator: In
                     values:
                     - csi-provisioner
                 topologyKey: kubernetes.io/hostname
         tolerations:
         - effect: NoSchedule
           operator: Exists
           key: node-role.kubernetes.io/master
         - effect: NoSchedule
           operator: Exists
           key: node.cloudprovider.kubernetes.io/uninitialized
         serviceAccount: csi-admin
         hostPID: true
         priorityClassName: system-node-critical
         containers:
           - name: external-disk-provisioner
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-provisioner:v3.0.0-080f01e64-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             args:
               - "--csi-address=$(ADDRESS)"
               - "--feature-gates=Topology=True"
               - "--volume-name-prefix=disk"
               - "--strict-topology=true"
               - "--timeout=150s"
               - "--leader-election=true"
               - "--retry-interval-start=500ms"
               - "--extra-create-metadata=true"
               - "--default-fstype=ext4"
               - "--v=5"
             env:
               - name: ADDRESS
                 value: /var/lib/kubelet/csi-provisioner/diskplugin.csi.alibabacloud.com/csi.sock
             volumeMounts:
               - name: disk-provisioner-dir
                 mountPath: /var/lib/kubelet/csi-provisioner/diskplugin.csi.alibabacloud.com
           - name: external-disk-attacher
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-attacher:v3.3-72dd428b-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             args:
               - "--v=5"
               - "--csi-address=$(ADDRESS)"
               - "--leader-election=true"
             env:
               - name: ADDRESS
                 value: /var/lib/kubelet/csi-provisioner/diskplugin.csi.alibabacloud.com/csi.sock
             volumeMounts:
               - name: disk-provisioner-dir
                 mountPath: /var/lib/kubelet/csi-provisioner/diskplugin.csi.alibabacloud.com
           - name: external-disk-resizer
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-resizer:v1.3-ca84e84-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 8Gi
             args:
               - "--v=5"
               - "--csi-address=$(ADDRESS)"
               - "--leader-election"
             env:
               - name: ADDRESS
                 value: /var/lib/kubelet/csi-provisioner/diskplugin.csi.alibabacloud.com/csi.sock
             volumeMounts:
               - name: disk-provisioner-dir
                 mountPath: /var/lib/kubelet/csi-provisioner/diskplugin.csi.alibabacloud.com
           - name: external-nas-provisioner
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-provisioner:v3.0.0-080f01e64-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             args:
               - "--csi-address=$(ADDRESS)"
               - "--volume-name-prefix=nas"
               - "--timeout=150s"
               - "--leader-election=true"
               - "--retry-interval-start=500ms"
               - "--default-fstype=nfs"
               - "--v=5"
             env:
               - name: ADDRESS
                 value: /var/lib/kubelet/csi-provisioner/nasplugin.csi.alibabacloud.com/csi.sock
             volumeMounts:
               - name: nas-provisioner-dir
                 mountPath: /var/lib/kubelet/csi-provisioner/nasplugin.csi.alibabacloud.com
           - name: external-nas-resizer
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-resizer:v1.3-ca84e84-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 8Gi
             args:
               - "--v=5"
               - "--csi-address=$(ADDRESS)"
               - "--leader-election"
             env:
               - name: ADDRESS
                 value: /var/lib/kubelet/csi-provisioner/nasplugin.csi.alibabacloud.com/csi.sock
             volumeMounts:
               - name: nas-provisioner-dir
                 mountPath: /var/lib/kubelet/csi-provisioner/nasplugin.csi.alibabacloud.com
           - name: external-oss-provisioner
             args:
               - --csi-address=$(ADDRESS)
               - --volume-name-prefix=oss
               - --timeout=150s
               - --leader-election=true
               - --retry-interval-start=500ms
               - --default-fstype=ossfs
               - --v=5
             env:
             - name: ADDRESS
               value: /var/lib/kubelet/csi-provisioner/ossplugin.csi.alibabacloud.com/csi.sock
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-provisioner:v3.0.0-080f01e64-aliyun
             resources:
               limits:
                 cpu: 500m
                 memory: 1Gi
               requests:
                 cpu: 10m
                 memory: 16Mi
             volumeMounts:
             - mountPath: /var/lib/kubelet/csi-provisioner/ossplugin.csi.alibabacloud.com
               name: oss-provisioner-dir
           - name: external-csi-snapshotter
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-snapshotter:v4.0.0-a230d5b3-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             args:
               - "--v=5"
               - "--csi-address=$(ADDRESS)"
               - "--leader-election=true"
               - "--extra-create-metadata=true"
             env:
               - name: ADDRESS
                 value: /csi/csi.sock
             volumeMounts:
               - name: disk-provisioner-dir
                 mountPath: /csi
           - name: external-snapshot-controller
             image: registry.cn-hangzhou.aliyuncs.com/acs/snapshot-controller:v4.0.0-a230d5b3-aliyun
             resources:
               requests:
                 cpu: 10m
                 memory: 16Mi
               limits:
                 cpu: 500m
                 memory: 1024Mi
             args:
               - "--v=5"
               - "--leader-election=true"
           - name: csi-provisioner
             securityContext:
               privileged: true
             image: registry.cn-hangzhou.aliyuncs.com/acs/csi-plugin:v1.24.6-55c95dd-aliyun
             args:
               - "--endpoint=$(CSI_ENDPOINT)"
               - "--v=2"
               - "--driver=nas,disk,oss"
             env:
               - name: CSI_ENDPOINT
                 value: unix://var/lib/kubelet/csi-provisioner/driverplugin.csi.alibabacloud.com-replace/csi.sock
               - name: MAX_VOLUMES_PERNODE
                 value: "15"
               - name: SERVICE_TYPE
                 value: "provisioner"
               - name: "CLUSTER_ID"
                 value: "CLUSTER_ID"
             livenessProbe:
               httpGet:
                 path: /healthz
                 port: healthz
                 scheme: HTTP
               initialDelaySeconds: 10
               periodSeconds: 30
               timeoutSeconds: 5
               failureThreshold: 5
             readinessProbe:
               httpGet:
                 path: /healthz
                 port: healthz
               initialDelaySeconds: 5
               periodSeconds: 20
             ports:
               - name: healthz
                 containerPort: 11270
             volumeMounts:
               - name: host-log
                 mountPath: /var/log/
               - name: disk-provisioner-dir
                 mountPath: /var/lib/kubelet/csi-provisioner/diskplugin.csi.alibabacloud.com
               - name: nas-provisioner-dir
                 mountPath: /var/lib/kubelet/csi-provisioner/nasplugin.csi.alibabacloud.com
               - name: oss-provisioner-dir
                 mountPath: /var/lib/kubelet/csi-provisioner/ossplugin.csi.alibabacloud.com
               - mountPath: /var/addon
                 name: addon-token
                 readOnly: true
               - mountPath: /mnt
                 mountPropagation: Bidirectional
                 name: host-dev
               - mountPath: /host/etc
                 name: etc
             resources:
               limits:
                 cpu: 500m
                 memory: 1024Mi
               requests:
                 cpu: 100m
                 memory: 128Mi
         volumes:
           - name: disk-provisioner-dir
             emptyDir: {}
           - name: nas-provisioner-dir
             emptyDir: {}
           - name: oss-provisioner-dir
             emptyDir: {}
           - name: host-log
             hostPath:
               path: /var/log/
           - name: etc
             hostPath:
               path: /etc
               type: ""
           - name: host-dev
             hostPath:
               path: /mnt
               type: ""
           - name: addon-token
             secret:
               defaultMode: 420
               optional: true
               items:
               - key: addon.token.config
                 path: token-config
               secretName: addon.csi.token

Déployez csi-plugin et csi-provisioner dans le cluster :

   kubectl apply -f csi-plugin.yaml -f csi-provisioner.yaml

Vérifiez que CSI est en cours d'exécution : Sortie attendue : Si tous les pods affichent l'état Running, CSI est installé.

   kubectl get pods -nkube-system | grep csi

   csi-plugin-577mm                              4/4     Running   0          3d20h
   csi-plugin-k9mzt                              4/4     Running   0          41d
   csi-provisioner-6b58f46989-8wwl5              9/9     Running   0          41d
   csi-provisioner-6b58f46989-qzh8l              9/9     Running   0          6d20h

Procédure

L'exemple suivant illustre la migration pour une charge de travail StatefulSet. La figure ci-dessous présente le flux de travail :

nas

Étape 1 : Vérifier l'état du volume

Interrogez l'état du pod : Sortie attendue :

   kubectl get pod

   NAME           READY   STATUS    RESTARTS   AGE
   nas-static-1   1/1     Running   0          11m

Recherchez le nom du PVC utilisé par le pod : Sortie attendue :

   kubectl describe pod nas-static-1 |grep ClaimName

   ClaimName:  nas-pvc

Vérifiez l'état du PVC : Sortie attendue :

   kubectl get pvc

   NAME      STATUS   VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
   nas-pvc   Bound    nas-pv   512Gi        RWX                         7m23s

Étape 2 : Créer un PV et un PVC gérés par CSI

Créez un nouveau PV et un nouveau PVC gérés par CSI qui pointent vers le même système de fichiers NAS. Choisissez l'une des options suivantes.

Option A : Conversion automatisée (CLI FlexVolume2CSI)

Utilisez la CLI FlexVolume2CSI pour convertir les définitions de PV et de PVC gérées par FlexVolume en équivalents gérés par CSI. L'outil génère un fichier nommé nas-pv-pvc-csi.yaml.
Appliquez le fichier généré :
```
   kubectl apply -f nas-pv-pvc-csi.yaml
```

Vérifiez l'état du PVC : Sortie attendue :

   kubectl get pvc

   NAME          STATUS   VOLUME       CAPACITY   ACCESS MODES   STORAGECLASS   AGE
   nas-pvc       Bound    nas-pv       512Gi      RWX            nas            30m
   nas-pvc-csi   Bound    nas-pv-csi   512Gi      RWX            nas            2s

Option B : Conversion manuelle

Sauvegardez les définitions existantes de PV et de PVC FlexVolume. Sauvegardez le PVC : Sortie attendue : Sauvegardez le PV : Sortie attendue :

   kubectl get pvc nas-pvc -oyaml > nas-pvc-flexvolume.yaml
   cat nas-pvc-flexvolume.yaml

   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: nas-pvc
     namespace: default
   spec:
     accessModes:
     - ReadWriteMany
     resources:
       requests:
         storage: 512Gi
     selector:
       matchLabels:
         alicloud-pvname: nas-pv
     storageClassName: nas

   kubectl get pv nas-pv -oyaml > nas-pv-flexvolume.yaml
   cat nas-pv-flexvolume.yaml

   apiVersion: v1
   kind: PersistentVolume
   metadata:
     labels:
       alicloud-pvname: nas-pv
     name: nas-pv
   spec:
     accessModes:
     - ReadWriteMany
     capacity:
       storage: 512Gi
     flexVolume:
       driver: alicloud/nas
       options:
         path: /aliyun
         server: ***.***.nas.aliyuncs.com
         vers: "3"
     persistentVolumeReclaimPolicy: Retain
     storageClassName: nas

Créez un PV et un PVC gérés par CSI. Créez un fichier nommé nas-pv-pvc-csi.yaml avec le contenu suivant : Appliquez le fichier : Vérifiez l'état du PVC : Sortie attendue :

   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: nas-pvc-csi
     namespace: default
   spec:
     accessModes:
     - ReadWriteMany
     resources:
       requests:
         storage: 512Gi
     selector:
       matchLabels:
         alicloud-pvname: nas-pv-csi
     storageClassName: nas
   ---
   apiVersion: v1
   kind: PersistentVolume
   metadata:
     labels:
       alicloud-pvname: nas-pv-csi
     name: nas-pv-csi
   spec:
     accessModes:
     - ReadWriteMany
     capacity:
       storage: 512Gi
     csi:
       driver: nasplugin.csi.alibabacloud.com
       volumeHandle: nas-pv-csi
       volumeAttributes:
         server: "***.***.nas.aliyuncs.com"
         path: "/aliyun"
     mountOptions:
     - nolock,tcp,noresvport
     - vers=3
     persistentVolumeReclaimPolicy: Retain
     storageClassName: nas

   kubectl apply -f nas-pv-pvc-csi.yaml

   kubectl get pvc

   NAME      STATUS   VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
   nas-pvc   Bound    nas-pv   512Gi        RWX                         7m23s

Étape 3 : Mettre à jour l'application

Modifiez la configuration du StatefulSet :
```
   kubectl edit sts nas-static
```

Mettez à jour la revendication de volume pour référencer le PVC géré par CSI :

   volumes:
         - name: pvc-nas
           persistentVolumeClaim:
             claimName: nas-pvc-csi

Confirmez le redémarrage du pod : Sortie attendue :

   kubectl get pod

   NAME           READY   STATUS    RESTARTS   AGE
   nas-static-1   1/1     Running   0          70s

Vérifiez que le volume NAS est monté via CSI : Si la migration a réussi, la sortie affiche kubernetes.io~csi dans le chemin de montage :

   kubectl exec nas-static-1 -- mount |grep nas

   # View the mount information
   ***.***.nas.aliyuncs.com:/aliyun on /var/lib/kubelet/pods/ac02ea3f-125f-4b38-9bcf-9b117f62***/volumes/kubernetes.io~csi/nas-pv-csi/mount type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,noresvport,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.XX.XX,mountvers=3,mountport=2049,mountproto=tcp,local_lock=all,addr=192.168.XX.XX)

Étape 4 : Désinstaller FlexVolume

Connectez-vous à la console OpenAPI Explorer et appelez l'opération UnInstallClusterAddons pour désinstaller le plug-in FlexVolume. Pour plus d'informations, consultez la rubrique Désinstallation de composants d'un cluster.
- ClusterId: ID de votre cluster. Vous pouvez le trouver dans l'onglet Basic Information de la page des détails de votre cluster.
- name: Définissez la valeur sur flexvolume.

Supprimez les composants alicloud-disk-controller et alicloud-nas-controller :

   kubectl delete deploy -n kube-system alicloud-disk-controller alicloud-nas-controller

Vérifiez que FlexVolume est entièrement désinstallé : Si aucune sortie n'est renvoyée, FlexVolume a été complètement supprimé.
```
   kubectl get pods -n kube-system | grep 'flexvolume\|alicloud-disk-controller\|alicloud-nas-controller'
```

Supprimez les StorageClasses FlexVolume (provisioner : alicloud/disk) : Sortie attendue :

   kubectl delete storageclass alicloud-disk-available alicloud-disk-efficiency alicloud-disk-essd alicloud-disk-ssd

   storageclass.storage.k8s.io "alicloud-disk-available" deleted
   storageclass.storage.k8s.io "alicloud-disk-efficiency" deleted
   storageclass.storage.k8s.io "alicloud-disk-essd" deleted
   storageclass.storage.k8s.io "alicloud-disk-ssd" deleted

Étape 5 : Installer CSI via l'API

Connectez-vous à la console OpenAPI Explorer et appelez l'opération InstallClusterAddons pour installer CSI. Pour plus d'informations, consultez la rubrique Installation d'un composant dans un cluster ACK.
- ClusterId: ID de votre cluster.
- name: Définissez la valeur sur csi-provisioner.
- version: La dernière version est automatiquement spécifiée. Pour plus de détails sur les versions, consultez la rubrique csi-provisioner.

Vérifiez que CSI est en cours d'exécution : Sortie attendue : Si tous les pods affichent l'état Running, CSI est installé.

   kubectl get pods -nkube-system | grep csi

   csi-plugin-577mm                              4/4     Running   0          3d20h
   csi-plugin-k9mzt                              4/4     Running   0          41d
   csi-provisioner-6b58f46989-8wwl5              9/9     Running   0          41d
   csi-provisioner-6b58f46989-qzh8l              9/9     Running   0          6d20h

Étape 6 : Mettre à jour les configurations des nœuds

Déployez un DaemonSet pour définir le paramètre kubelet --enable-controller-attach-detach sur true sur tous les nœuds existants. Supprimez le DaemonSet une fois la mise à jour terminée.

Important

Ce DaemonSet redémarre kubelet sur chaque nœud. Évaluez l'impact sur les applications en cours d'exécution avant de poursuivre.

Créez un fichier avec le contenu suivant et appliquez-le avec kubectl apply -f <filename>.yaml :

kind: DaemonSet
apiVersion: apps/v1
metadata:
  name: kubelet-set
spec:
  selector:
    matchLabels:
      app: kubelet-set
  template:
    metadata:
      labels:
        app: kubelet-set
    spec:
      tolerations:
        - operator: "Exists"
      hostNetwork: true
      hostPID: true
      containers:
        - name: kubelet-set
          securityContext:
            privileged: true
            capabilities:
              add: ["SYS_ADMIN"]
            allowPrivilegeEscalation: true
          image: registry.cn-hangzhou.aliyuncs.com/acs/csi-plugin:v1.26.5-56d1e30-aliyun
          imagePullPolicy: "Always"
          env:
          - name: enableADController
            value: "true"
          command: ["sh", "-c"]
          args:
          - echo "Starting kubelet flag set to $enableADController";
            ifFlagTrueNum=`cat /host/etc/systemd/system/kubelet.service.d/10-kubeadm.conf | grep enable-controller-attach-detach=$enableADController | grep -v grep | wc -l`;
            echo "ifFlagTrueNum is $ifFlagTrueNum";
            if [ "$ifFlagTrueNum" = "0" ]; then
                curValue="true";
                if [ "$enableADController" = "true" ]; then
                    curValue="false";
                fi;
                sed -i "s/enable-controller-attach-detach=$curValue/enable-controller-attach-detach=$enableADController/" /host/etc/systemd/system/kubelet.service.d/10-kubeadm.conf;
                restartKubelet="true";
                echo "current value is $curValue, change to expect "$enableADController;
            fi;
            if [ "$restartKubelet" = "true" ]; then
                /nsenter --mount=/proc/1/ns/mnt systemctl daemon-reload;
                /nsenter --mount=/proc/1/ns/mnt service kubelet restart;
                echo "restart kubelet";
            fi;
            while true;
            do
                sleep 5;
            done;
          volumeMounts:
          - name: etc
            mountPath: /host/etc
      volumes:
        - name: etc
          hostPath:
            path: /etc