Use NAS dynamic volumes

kubectl

1. Create a file named alicloud-nas-subpath.yaml with the following content:

   apiVersion: storage.k8s.io/v1
   kind: StorageClass
   metadata:
     # The name of the StorageClass, which must be unique within the cluster.
     name: alicloud-nas-subpath  
   mountOptions:
   - nolock,tcp,noresvport
   - vers=3
   parameters:
     # Set to subpath.
     volumeAs: subpath
     # The format of the server field is <nas-server-address>:/<path>.
     server: "0cd8b4a576-g****.cn-hangzhou.nas.aliyuncs.com:/k8s"
     archiveOnDelete: "true"
   provisioner: nasplugin.csi.alibabacloud.com
   reclaimPolicy: Retain
   allowVolumeExpansion: true

   Parameter		Description
   mountOptions		The mount options for NAS, including the NFS protocol version. By default, volumes are mounted using NFSv3. You can specify a different version with an option such as vers=4.0. For information about the NFS protocols supported by different NAS types, see NFS protocols.
   parameters.volumeAs		The volume provisioning mode. Set to subpath.
   parameters.server		The NAS mount target and the subpath to mount, in the format <nas-server-address>:/<path>. <nas-server-address>: The mount target of the NAS file system. For more information, see Manage mount targets. :/<path>: The NAS subpath to mount. If this parameter is not set or the specified subpath does not exist, the root directory is mounted by default. General-purpose NAS: The root directory is /. Extreme NAS: The root directory is /share. When you mount a subpath, the path must start with /share, such as /share/data.
   parameters.archiveOnDelete		Specifies whether to delete the data on the backend storage when a PVC is deleted and its reclaimPolicy is set to Delete. This option acts as a safeguard to prevent accidental data loss on shared NAS storage. true (default): The directory and its files are not deleted. Instead, they are archived and renamed in the format archived-{pvName}.{timestamp}. false: The corresponding directory and its data are permanently deleted. This operation deletes the NAS subpath and its files, not the NAS file system itself. To delete a NAS file system, see Delete a file system. In scenarios where PVs are frequently created and deleted, setting this parameter to false may cause the CSI controller's task queue to become blocked, which prevents new PVs from being created. For more information, see The controller's task queue is full and new PVs cannot be created when you use a dynamic NAS volume.
   provisioner		The driver. Set this parameter to nasplugin.csi.alibabacloud.com when you use the Alibaba Cloud NAS CSI plug-in.
   reclaimPolicy		The reclaim policy of the PV. Delete (default): When the PVC is deleted, the backend storage data is processed based on the archiveOnDelete setting. Retain: When the PVC is deleted, the PV and the data in the NAS file system are not deleted and must be deleted manually. This policy is recommended for scenarios that require high data security to prevent accidental data loss.
   allowVolumeExpansion		Supported only by General-purpose NAS. Allows dynamic expansion of PVs created by this StorageClass by modifying the PVC capacity. This StorageClass uses the NAS directory quota feature to manage PV capacity, enabling precise size control. You can expand the volume online by editing the spec.resources.requests.storage field of the PVC. For more information, see Set directory quotas for dynamic NAS volumes. NAS directory quotas take effect asynchronously. If you perform high-speed, large-volume data writes immediately after a PV is created or expanded, you may exceed the specified capacity because the quota is not yet fully enforced. For more information, see Usage limits.

2. Create the StorageClass.

   kubectl create -f alicloud-nas-subpath.yaml

Console

1. Log on to the ACK console. In the left navigation pane, click Clusters.

2. On the Clusters page, click the name of your cluster. In the left navigation pane, click Volumes > StorageClasses.

3. Click Create, specify a unique name for the StorageClass within the cluster, select NAS as the PV Type, and then follow the on-screen instructions to create the StorageClass.

   The key parameters are described in the following table.

   Parameter	Description
   Select Mount Target	The mount target of the NAS file system.
   Volume Mode	The volume provisioning mode. Select Subdirectory. A subpath is automatically created under the specified mount path. Data is stored at <NAS mount target>:<mount path>/<pv-name>/.
   Mount Path	The NAS subdirectory to mount. If this parameter is not specified, the root directory is mounted by default. If the directory does not exist in the NAS file system, it is automatically created and then mounted. General-purpose NAS: The root directory is /. Extreme NAS: The root directory is /share. When you mount a subdirectory, the path must start with /share, such as /share/data.
   Reclaim Policy	The reclaim policy of the PV. Delete (default): When the PVC is deleted, the backend storage data is processed based on the archiveOnDelete setting. Retain: When the PVC is deleted, the PV and the data in the NAS file system are not deleted and must be deleted manually. This policy is recommended for scenarios that require high data security to prevent accidental data loss.
   Mount Options	The mount options for NAS, including the NFS protocol version. By default, volumes are mounted using NFSv3. You can specify a different version with an option such as vers=4.0. For information about the NFS protocols supported by different NAS types, see NFS protocols.

   After the StorageClass is created, you can view it in the StorageClasses list.

kubectl

1. Create a file named nas-pvc.yaml with the following content:

   kind: PersistentVolumeClaim
   apiVersion: v1
   metadata: 
     name: nas-csi-pvc
   spec:
     accessModes:
     - ReadWriteMany 
     # Specify the StorageClass to use.
     storageClassName: alicloud-nas-subpath  
     resources: 
       requests:
         # Declare the required capacity of the storage volume.
         storage: 20Gi  

   Parameter	Description
   accessModes	The access mode. Valid values: ReadWriteMany (default): The volume can be mounted as read-write by many nodes. ReadWriteOnce: The volume can be mounted as read-write by a single node. ReadOnlyMany: The volume can be mounted as read-only by many nodes.
   storageClassName	The name of the StorageClass to use.
   storage	The required capacity of the storage volume. By default, this declaration acts as a resource request and does not limit the actual storage space available to the pod. The capacity limit of a NAS file system is determined by its specifications. For more information, see General-purpose NAS and Extreme NAS. However, when allowVolumeExpansion in the StorageClass is set to true, this value becomes a strictly enforced hard limit. The CSI plug-in sets the NAS directory quota based on this configuration to limit the available capacity of the PV.

2. Create the PVC.

   kubectl create -f nas-pvc.yaml

3. Check the PV.

   kubectl get pv

   The expected output is similar to the following, which shows that the StorageClass automatically provisioned a PersistentVolume (PV) and bound it to the PVC.

   NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                 STORAGECLASS             VOLUMEATTRIBUTESCLASS   REASON   AGE
   nas-a7540d97-0f53-4e05-b7d9-557309******   20Gi       RWX            Retain           Bound    default/nas-csi-pvc   alicloud-nas-subpath     <unset>                          5m

Console

1. In the left navigation pane of the cluster management page, choose Storage > PVCs.

2. On the Persistent Volume Claims page, click Create, configure the PVC parameters, and then click Create.

   Parameter	Description
   PVC Type	Select NAS.
   Name	The name of the PVC. The name must be unique within the namespace.
   Allocation Mode	Select Use StorageClass.
   Existing Storage Class	Click Select Storage Class and choose the StorageClass that you created.
   Total Capacity	The required capacity of the storage volume. By default, this declaration acts as a resource request and does not limit the actual storage space available to the pod. The capacity limit of a NAS file system is determined by its specifications. For more information, see General-purpose NAS and Extreme NAS. However, when allowVolumeExpansion in the StorageClass is set to true, this value becomes a strictly enforced hard limit. The CSI plug-in sets the NAS directory quota based on this configuration to limit the available capacity of the PV.
   Access Mode	The access mode. Valid values: ReadWriteMany (default): The volume can be mounted as read-write by many nodes. ReadWriteOnce: The volume can be mounted as read-write by a single node. ReadOnlyMany: The volume can be mounted as read-only by many nodes.

kubectl

Create two Deployments that reference the same PVC to allow them to share the same subpath of the NAS file system.

To mount different subpaths from the same NAS file system to different pods, you must create a unique StorageClass and a corresponding PVC for each subpath.

1. Create two files named nginx-1.yaml and nginx-2.yaml with the following content.

   The configurations for both applications are nearly identical. They both reference the same PVC.

   • nginx-1.yaml

     apiVersion: apps/v1
     kind: Deployment
     metadata:
       name: nas-test-1     
       labels:
         app: nginx
     spec:
       selector:
         matchLabels:
           app: nginx
       template:
         metadata:
           labels:
             app: nginx
         spec:
           containers:
           - name: nginx
             image: anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
             ports:
             - containerPort: 80
             volumeMounts:
               - name: nas-pvc
                 # The mount path for the NAS volume inside the container.
                 mountPath: "/data"          
           volumes:
             - name: nas-pvc                 
               persistentVolumeClaim:
                 # Reference the previously created PVC.
                 claimName: nas-csi-pvc      

   • nginx-2.yaml

     apiVersion: apps/v1
     kind: Deployment
     metadata:
       name: nas-test-2     
       labels:
         app: nginx
     spec:
       selector:
         matchLabels:
           app: nginx
       template:
         metadata:
           labels:
             app: nginx
         spec:
           containers:
           - name: nginx
             image: anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
             ports:
             - containerPort: 80
             volumeMounts:
               - name: nas-pvc
                 # The mount path for the NAS volume inside the container.
                 mountPath: "/data"           
           volumes:
             - name: nas-pvc                 
               persistentVolumeClaim:
                 # Reference the previously created PVC.
                 claimName: nas-csi-pvc       

2. Create the two Deployments.

   kubectl create -f nginx-1.yaml -f nginx-2.yaml

3. Check the status of the pods.

   kubectl get pod -l app=nginx

   Expected output:

   NAME                         READY   STATUS    RESTARTS   AGE
   nas-test-1-b75d5b6bc-*****   1/1     Running   0          51s
   nas-test-2-b75d5b6bc-*****   1/1     Running   0          44s

4. Inspect each pod to verify that it uses the correct PersistentVolumeClaim (PVC).

   Replace <podName> with the actual name of each pod.

   kubectl describe pod <podName> | grep "ClaimName:"

   In the expected output, both pods use the same PVC, which confirms that they share the same subpath of the NAS file system.

Console

Repeat the following steps to create two Deployments that use the same PVC, which allows them to share the same subpath of the NAS file system.

1. On the ACK Clusters page, click the name of your cluster. In the left navigation pane, click Workloads > Deployments.

2. Click Create from Image and follow the on-screen instructions to configure and create the application.

   The key parameters are described below. You can keep the default values for other parameters. For more information, see Create a stateless application (Deployment).

   Section	Parameter	Description
   Basic Information	Replicas:	The number of replicas for the Deployment.
   Container	Image	The address of the image used to deploy the application.
   	Required Resources	The vCPU and memory resources required by the container.
   	Volumes	Click Add PVC and then configure the parameters. Mount Source: Select the PVC that you created. Container Path: Enter the path within the container where the NAS file system will be mounted.

   After the deployment is complete, you can click the application name on the Deployments page and check the Pods tab to confirm that the pods are running properly (their status is Running).

kubectl

Console

1. On the Clusters page, click the name of your cluster. In the left navigation pane, click Volumes > StorageClasses.

2. Click Create, specify a unique name for the StorageClass, and select NAS as the PV Type.

   Parameter	Description
   Select Mount Target	The mount target of the NAS file system.
   Volume Mode	The volume provisioning mode. In this example, select Shared Directory, which enables sharepath mode.
   Mount Path	The NAS subdirectory to mount. If this parameter is not specified, the root directory is mounted by default. If the directory does not exist in the NAS file system, it is automatically created and then mounted. General-purpose NAS: The root directory is /. Extreme NAS: The root directory is /share. When you mount a subdirectory, the path must start with /share, such as /share/data.
   Reclaim policy	For sharepath mode, this must be Retain.
   Mount options	The mount options for NAS, including the NFS protocol version. By default, volumes are mounted using NFSv3. You can specify a different version with an option such as vers=4.0. For information about the NFS protocols supported by different NAS types, see NFS protocols.

kubectl

1. Create two namespaces, ns1 and ns2.

   kubectl create ns ns1
   kubectl create ns ns2

2. Create a file named pvc.yaml with the following content to create a PVC with the same name in both the ns1 and ns2 namespaces.

   kind: PersistentVolumeClaim
   apiVersion: v1
   metadata: 
     name: nas-csi-pvc
     namespace: ns1
   spec:
     accessModes:
     - ReadWriteMany 
     storageClassName: alicloud-nas-sharepath
     resources: 
       requests:
         storage: 20Gi
   ---
   kind: PersistentVolumeClaim
   apiVersion: v1
   metadata: 
     name: nas-csi-pvc
     namespace: ns2
   spec:
     accessModes:
     - ReadWriteMany 
     storageClassName: alicloud-nas-sharepath
     resources: 
       requests:
         storage: 20Gi

   Parameter	Description
   accessModes	The access mode. Valid values: ReadWriteMany (default): The volume can be mounted as read-write by many nodes. ReadWriteOnce: The volume can be mounted as read-write by a single node. ReadOnlyMany: The volume can be mounted as read-only by many nodes.
   storageClassName	The name of the StorageClass to use.
   storage	The required capacity of the storage volume. By default, this declaration acts as a resource request and does not limit the actual storage space available to the pod. The capacity limit of a NAS file system is determined by its specifications. For more information, see General-purpose NAS and Extreme NAS. However, when allowVolumeExpansion in the StorageClass is set to true, this value becomes a strictly enforced hard limit. The CSI plug-in sets the NAS directory quota based on this configuration to limit the available capacity of the PV.

3. Create the PVCs.

   kubectl create -f pvc.yaml

4. Check the PV status to confirm that PVs have been automatically created and bound to the PVCs.

   kubectl get pv

   The expected output is similar to the following. The status of both PVs is Bound, and the CLAIM column shows that each PV is bound to a PVC in a different namespace (ns1/nas-csi-pvc and ns2/nas-csi-pvc).

   NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                 STORAGECLASS             VOLUMEATTRIBUTESCLASS   REASON   AGE
   nas-0b448885-6226-4d22-8a5b-d0768c******   20Gi       RWX            Retain           Bound    ns1/nas-csi-pvc       alicloud-nas-sharepath   <unset>                          74s
   nas-bcd21c93-8219-4a11-986b-fd934a******   20Gi       RWX            Retain           Bound    ns2/nas-csi-pvc       alicloud-nas-sharepath   <unset>                          74s

Console

1. Create namespaces.

   • On the Clusters page, click the name of your cluster. In the left navigation pane, click Namespaces and Quotas.

   • Click Launch and follow the on-screen instructions to create the ns1 and ns2 namespaces.

2. In the left navigation pane of the cluster management page, choose Storage > PVCs.

3. In the ns1 namespace, create a storage claim.

   On the Persistent Volume Claims page, select ns1 from the Namespace dropdown list and follow the on-screen instructions to create the PVC.

   Parameter	Description
   PVC Type	Select NAS.
   Name	The name of the PVC. The name must be unique within the namespace.
   Allocation Mode	Select Use StorageClass.
   Existing Storage Class	Click Select Storage Class and choose the StorageClass that you created.
   Capacity	The required capacity of the storage volume. By default, this declaration acts as a resource request and does not limit the actual storage space available to the pod. The capacity limit of a NAS file system is determined by its specifications. For more information, see General-purpose NAS and Extreme NAS. However, when allowVolumeExpansion in the StorageClass is set to true, this value becomes a strictly enforced hard limit. The CSI plug-in sets the NAS directory quota based on this configuration to limit the available capacity of the PV.
   Access Mode	The access mode. Valid values: ReadWriteMany (default): The volume can be mounted as read-write by many nodes. ReadWriteOnce: The volume can be mounted as read-write by a single node. ReadOnlyMany: The volume can be mounted as read-only by many nodes.

4. Follow the previous step to create another PVC in the ns2 namespace.

   After creation, return to the Persistent Volume Claims page. In both the ns1 and ns2 namespaces, confirm that both PVCs are bound to their automatically created PVs.

kubectl

1. Create two files named nginx-ns1.yaml and nginx-ns2.yaml with the following content.

   The configurations for both applications are nearly identical. They each bind to the PVC in their respective namespace.

   • nginx-ns1.yaml

     apiVersion: apps/v1
     kind: Deployment
     metadata:
       name: nas-test
       namespace: ns1   
     spec:
       selector:
         matchLabels:
           app: nginx
       template:
         metadata:
           labels:
             app: nginx
         spec:
           containers:
           - name: nginx
             image: anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
             ports:
             - containerPort: 80
             volumeMounts:
               - name: nas-pvc
                 mountPath: "/data"
           volumes:
             - name: nas-pvc
               persistentVolumeClaim:
                 claimName: nas-csi-pvc

   • nginx-ns2.yaml

     apiVersion: apps/v1
     kind: Deployment
     metadata:
       name: nas-test
       namespace: ns2   
     spec:
       selector:
         matchLabels:
           app: nginx
       template:
         metadata:
           labels:
             app: nginx
         spec:
           containers:
           - name: nginx
             image: anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
             ports:
             - containerPort: 80
             volumeMounts:
               - name: nas-pvc
                 mountPath: "/data"
           volumes:
             - name: nas-pvc
               persistentVolumeClaim:
                 claimName: nas-csi-pvc

2. Create the two Deployments.

   kubectl create -f nginx-ns1.yaml -f nginx-ns2.yaml

3. Check the Pod status.

   kubectl get pod -A -l app=nginx

   Expected output:

   NAMESPACE   NAME                         READY   STATUS    RESTARTS   AGE
   ns1         nas-test-b75d5b6bc-*****     1/1     Running   0          2m19s
   ns2         nas-test-b75d5b6bc-*****     1/1     Running   0          2m11s

4. Check the detailed configuration of a Pod to confirm the PVC mount.

   Replace <namespace-name> and <pod-name> with the actual namespace and Pod name.

   kubectl describe pod -n <namespace-name> <pod-name> | grep "ClaimName:"

   In the expected output, the two Pods mount ns1/nas-csi-pvc and ns2/nas-csi-pvc respectively.

Console

1. On the ACK Clusters page, click the name of your cluster. In the left navigation pane, click Workloads > Deployments.

2. In the ns1 namespace, create a Deployment and mount the corresponding PVC.

   1. Select Namespace from the Namespace dropdown list and click Create from Image.

   2. Follow the on-screen instructions to create the application.

      The key parameters are described below. Leave other parameters at their default values. For more information, see Create a stateless workload (Deployment).

      Section	Parameter	Description
      Basic Information	Replicas:	The replica count of the Deployment.
      Container	Image	The address of the image used to deploy the application.
      	Required Resources	The required vCPU and memory resources.
      	Volumes	Click Add PVC and configure the parameters. Mount Source: Select the PVC that you created. Container Path: Enter the path within the container where the NAS file system will be mounted, such as /data.

3. Follow the previous step to create another Deployment in the ns2 namespace and mount the corresponding PVC.

   Return to the Deployments page. In the ns1 and ns2 namespaces, check the status of each Deployment to confirm that the Pods are running and have mounted the correct PVCs.