Mount a dynamically provisioned NAS volume using NFS

kubectl

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

   StorageClass parameters (subpath)

   Parameter	Description	Default
   mountOptions	Mount options for NAS, including the NFS protocol version. NAS uses NFS v3 by default. To use a different version, set vers=4.0. For supported NFS versions per NAS type, see NFS protocol.	vers=3
   parameters.volumeAs	Mount mode. Set to subpath.	--
   parameters.server	The NAS mount target address and subdirectory path. Format: <mount-target-address>:/<path>. - <mount-target-address>: The mount target address. See Manage mount targets. - :/<path>: The NAS subdirectory to mount. If unset or if the subdirectory does not exist, the root directory is mounted by default. General-purpose NAS root: /. Extreme NAS root: /share (subdirectory paths must start with /share, for example, /share/data).	Root directory
   parameters.archiveOnDelete	Controls whether backend data is permanently deleted when you delete a PVC. This setting applies only when reclaimPolicy is Delete. - true: Data is not deleted. The subdirectory is archived and renamed to archived-{pvName}.{timestamp}. - false: The subdirectory and its data are permanently deleted (only the subdirectory, not the NAS file system). Note Setting this to false with frequent PV creation and deletion may block the CSI controller task queue and prevent new PVs from being provisioned. See CSI controller task queue is full.	true
   provisioner	The CSI driver. Set to nasplugin.csi.alibabacloud.com for Alibaba Cloud NAS.	--
   reclaimPolicy	Reclaim policy for the PV. Delete: Handles backend data based on the archiveOnDelete setting. Retain: The PV and NAS data remain intact when you delete the PVC. You must delete them manually. Use this for production environments.	Delete
   allowVolumeExpansion	Enables online expansion of PVs by modifying the PVC capacity. Supported only for General-purpose NAS. The CSI driver uses NAS directory quota to enforce capacity limits. To expand, edit the spec.resources.requests.storage field in the PVC. See Set directory quotas for NAS dynamically provisioned volumes. Note NAS directory quotas are applied asynchronously. Immediately after creating or expanding a PV, high-speed bulk writes may exceed the quota before it fully takes effect. See Limits.	--

      apiVersion: storage.k8s.io/v1
      kind: StorageClass
      metadata:
        # StorageClass name. Must be unique in the cluster.
        name: alicloud-nas-subpath
      mountOptions:
      - nolock,tcp,noresvport
      - vers=3
      parameters:
        # Mount mode: subpath creates a subdirectory per PV.
        volumeAs: subpath
        # NAS mount target address and base path. Format: <mount-target-address>:/<path>
        server: "0cd8b4a576-g****.cn-hangzhou.nas.aliyuncs.com:/k8s"
        # Archive (not delete) subdirectory data when PVC is deleted with reclaimPolicy: Delete.
        archiveOnDelete: "true"
      provisioner: nasplugin.csi.alibabacloud.com
      reclaimPolicy: Retain
      allowVolumeExpansion: true

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 the target cluster. In the left navigation pane, choose Volumes > StorageClasses.

3. Click Create. Enter a unique name for the StorageClass, set PV Type to NAS, and complete the remaining fields as described below.

   Configuration item	Description
   Select Mount Target	The mount target address of the NAS file system.
   Volume Mode	Select Subdirectory (subpath). The system automatically creates a subdirectory under the mount path. Data is stored at <NAS mount target>:<mount path>/<pv-name>/.
   Mount Path	The subdirectory of the NAS file system to mount. If you leave this blank, the root directory is mounted by default. If the directory does not exist, it is automatically created. General-purpose NAS: Root directory is /. Extreme NAS: Root directory is /share. Subdirectory paths must start with /share (for example, /share/data).
   Reclaim Policy	Reclaim policy for the PV. Delete (default): Handles backend data based on the archiveOnDelete setting. Retain: The PV and NAS data remain intact. You must delete them manually.
   Mount Options	Mount options for NAS, including the NFS protocol version. The default version is NFS v3. To use a different version, set vers=4.0. For supported versions, see NFS protocol.

After the StorageClass is created, you can view it in the Storage Classes list on the console.

kubectl

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

   PVC parameters

   Parameter	Description	Default
   accessModes	Volume access mode. This field is required. Valid values: ReadWriteMany: Read-write by many nodes. Recommended for NAS. ReadWriteOnce: Read-write by a single node. ReadOnlyMany: Read-only by many nodes.	ReadWriteMany
   storageClassName	The name of the StorageClass to bind.	--
   storage	Requested volume capacity. By default, this is a resource request and does not restrict the actual storage available to the pod. The maximum NAS capacity depends on the specification. See General-purpose NAS and Extreme NAS. When allowVolumeExpansion is set to true in the StorageClass, this value becomes a hard limit enforced by NAS directory quota.	--

      kind: PersistentVolumeClaim
      apiVersion: v1
      metadata:
        name: nas-csi-pvc
      spec:
        accessModes:
        - ReadWriteMany
        # Reference the StorageClass created in Step 1.
        storageClassName: alicloud-nas-subpath
        resources:
          requests:
            # Requested volume capacity. See the storage parameter description below.
            storage: 20Gi

2. Create the PVC.

      kubectl create -f nas-pvc.yaml

3. Verify that the PV was automatically created and bound:

      kubectl get pv

      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, choose Volumes > Persistent Volume Claims.

2. On the Persistent Volume Claims page, click Create. Configure the PVC as described below and click Create.

   Configuration item	Description
   PVC Type	Select NAS.
   Name	PVC name. Must be unique within the namespace.
   Allocation Mode	Select Use StorageClass.
   Existing Storage Class	Click Select and choose the StorageClass you created earlier.
   Capacity	Requested volume capacity. By default, this is a resource request and does not restrict the actual storage available to the pod. The maximum NAS capacity depends on the specification. See General-purpose NAS and Extreme NAS. When allowVolumeExpansion is set to true in the StorageClass, this value becomes a hard limit enforced by NAS directory quota.
   Access Mode	Volume access mode. Valid values: ReadWriteMany (default): Read-write by many nodes. ReadWriteOnce: Read-write by a single node. ReadOnlyMany: Read-only by many nodes.

kubectl

1. Create two files named nginx-1.yaml and nginx-2.yaml with the following content. 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
                  # Path inside the container where NAS is mounted.
                  mountPath: "/data"
            volumes:
              - name: nas-pvc
                persistentVolumeClaim:
                  # Reference the PVC created in Step 2.
                  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
                  # Path inside the container where NAS is mounted.
                  mountPath: "/data"
            volumes:
              - name: nas-pvc
                persistentVolumeClaim:
                  # Reference the PVC created in Step 2.
                  claimName: nas-csi-pvc

2. Create the two Deployments.

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

3. Check the pod status:

      kubectl get pod -l app=nginx

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

4. Confirm that the PVC is mounted. Replace <podName> with the actual pod name. Both pods should show nas-csi-pvc as the claim name, confirming they share the same NAS subdirectory.

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

Console

Repeat the following steps to create two Deployments that mount the same PVC.

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

2. Click Create from Image. Configure the application as described below. Keep other parameters at their default values. For more information, see Create a Deployment.

   Configuration page	Parameter	Description
   Basic Information	Replicas	Number of replicas for the Deployment.
   Container	Image Name	Image address used to deploy the application.
   	Required Resources	vCPU and memory resources required.
   	Volume	Click Add PVC, then complete: Mount Source: Select the PVC created earlier. Container Path: Path in the container where the NAS file system is mounted.

After the Deployment completes, click the application name on the Stateless page and confirm that the pod status is Running on the Container Group tab.

To verify that storage is shared and persistent, see Verify shared and persistent storage.

kubectl

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

   StorageClass parameters (sharepath)

   Parameter	Description	Default
   mountOptions	Mount options for NAS, including the NFS protocol version. The default version is NFS v3. To use a different version, set vers=4.0. For supported versions, see NFS protocol.	vers=3
   parameters.volumeAs	Mount mode. Set to sharepath.	--
   parameters.server	The NAS mount target address and subdirectory path. Format: <mount-target-address>:/<path>. - <mount-target-address>: The mount target address. See Manage mount targets. - :/<path>: The NAS subdirectory to mount. If unset or if the subdirectory does not exist, the root directory is mounted by default. General-purpose NAS root: /. Extreme NAS root: /share (subdirectory paths must start with /share).	Root directory
   provisioner	The CSI driver. Set to nasplugin.csi.alibabacloud.com.	--
   reclaimPolicy	For sharepath, always set this to Retain to prevent data loss. The default Kubernetes value is Delete.	--

      apiVersion: storage.k8s.io/v1
      kind: StorageClass
      metadata:
        name: alicloud-nas-sharepath
      mountOptions:
      - nolock,tcp,noresvport
      - vers=3
      parameters:
        # Mount mode: sharepath maps all PVs to the same directory.
        volumeAs: sharepath
        # NAS mount target address and shared directory path.
        server: "0cd8b4a576-g****.cn-hangzhou.nas.aliyuncs.com:/k8s"
      provisioner: nasplugin.csi.alibabacloud.com
      # Sharepath only supports Retain.
      reclaimPolicy: Retain

2. Create the StorageClass.

      kubectl create -f alicloud-nas-sharepath.yaml

Console

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

2. Click Create. Enter a unique name for the StorageClass, set PV Type to NAS, and complete the remaining fields as described below.

   Configuration item	Description
   Select mount target	The mount target address of the NAS file system.
   Volume mode	Select Shared directory (sharepath).
   Mount path	The subdirectory of the NAS file system to mount. If you leave this blank, the root directory is mounted by default. If the directory does not exist, it is automatically created. - General-purpose NAS: Root directory is /. - Extreme NAS: Root directory is /share. Subdirectory paths must start with /share.
   Reclaim Policy	For sharepath, set this to Retain.
   Mount options	Mount options for NAS, including the NFS protocol version. The default version is NFS v3. To use a different version, set vers=4.0. For supported versions, see NFS protocol.

kubectl

1. Create the ns1 and ns2 namespaces.

      kubectl create ns ns1
      kubectl create ns ns2

2. Create a file named pvc.yaml with the following content.

   PVC parameters

   Parameter	Description	Default
   accessModes	Volume access mode. This field is required. Valid values: ReadWriteMany: Read-write by many nodes. Recommended for NAS. ReadWriteOnce: Read-write by a single node. ReadOnlyMany: Read-only by many nodes.	ReadWriteMany
   storageClassName	The name of the StorageClass to bind.	--
   storage	Requested volume capacity. By default, this is a resource request and does not restrict actual storage. The maximum NAS capacity depends on the specification. See General-purpose NAS and Extreme NAS. When allowVolumeExpansion is set to true in the StorageClass, this value becomes a hard limit enforced by NAS directory quota.	--

      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

3. Create the PVCs.

      kubectl create -f pvc.yaml

4. Verify that PVs were automatically created and bound. Both PVs should show Bound status, each linked to a PVC in a different namespace:

      kubectl get pv

      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 cluster name. In the left navigation pane, click Namespaces and Quotas.

   • Click Create. Follow the prompts to create the ns1 and ns2 namespaces.

2. In the left navigation pane, choose Volumes > Persistent Volume Claims.

3. Create a PVC in the ns1 namespace. Set Namespace to ns1 and configure the PVC as described below.

   Configuration item	Description
   PVC Type	Select NAS.
   Name	PVC name. Must be unique within the namespace.
   Allocation Mode	Select Use StorageClass.
   Existing Storage Class	Click Select and choose the StorageClass created earlier.
   Capacity	Requested volume capacity. By default, this is a resource request and does not restrict actual storage. When allowVolumeExpansion is set to true in the StorageClass, this value becomes a hard limit enforced by NAS directory quota.
   Access Mode	Volume access mode. Valid values: ReadWriteMany (default): Read-write by many nodes. ReadWriteOnce: Read-write by a single node. ReadOnlyMany: Read-only by many nodes.

4. Repeat the previous step to create a PVC in the ns2 namespace.

After the PVCs are created, return to the Persistent Volume Claims page and confirm that the PVCs in ns1 and ns2 are bound to automatically created PVs.

kubectl

1. Create two files named nginx-ns1.yaml and nginx-ns2.yaml. Each binds the PVC in its namespace.

   nginx-ns1.yaml

      apiVersion: apps/v1
      kind: Deployment
      metadata:
        name: nas-test
        # Deploy to the ns1 namespace.
        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
        # Deploy to the ns2 namespace.
        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

      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. Confirm that the PVC is mounted. Replace <namespace-name> and <pod-name> with actual values. The two pods mount ns1/nas-csi-pvc and ns2/nas-csi-pvc, respectively. Both point to the same NAS directory.

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

Console

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

2. Create a Deployment in the ns1 namespace and mount the corresponding PVC.

   1. Set Namespace to ns1 and click Create from Image.

   2. Complete the application creation as described below. Keep other parameters at their default values. For more information, see Create a Deployment.

   Configuration page	Parameter	Description
   Basic Information	Replicas	Number of replicas for the Deployment.
   Container	Image Name	Image address used to deploy the application.
   	Required Resources	vCPU and memory resources required.
   	Volumes	Click PVC, then complete: Mount Source: Select the PVC created earlier. Container Path: Path in the container where the NAS file system is mounted (for example, /data).

3. Repeat the previous step to create a Deployment in the ns2 namespace and mount the corresponding PVC.

Return to the Stateless page to check the Deployment status in both namespaces and confirm that pods are running with their PVCs mounted.

To verify that storage is shared and persistent, see Verify shared and persistent storage.