File Storage NAS:Mount a dynamically provisioned NAS volume using NFS

Use kubectl

1. Create a StorageClass

1. Create alicloud-nas-subpath.yaml with the following content, and update the parameters for your environment:

   Parameter	Description	Default
   allowVolumeExpansion	(General-purpose NAS only) Set to true to enable NAS directory quotas on dynamically provisioned PVs, allowing you to expand the volume by modifying the PVC. The quota takes effect asynchronously and may be briefly exceeded under heavy writes. For details, see Manage directory quotas.	—
   mountOptions	NFS mount options, including the NFS version.	—
   volumeAs	The mount mode. Set to subpath.	—
   server	The mount target domain and base path. Replace with your actual mount target. To find the domain name, see Manage mount targets.	/ (root)
   provisioner	The CSI driver. Must be nasplugin.csi.alibabacloud.com.	—
   reclaimPolicy	Controls what happens to PV data when a PVC is deleted.	Delete
   archiveOnDelete	(When reclaimPolicy: Delete) Controls whether PV data is deleted or archived. true: renames the subdirectory to archived-{pvName}.{timestamp}. false: permanently deletes the data. Important Do not set this to false during high-traffic periods. To delete backend data, you must set archiveOnDelete: false using kubectl — the console cannot configure this parameter.	true

   allowVolumeExpansion: true
   apiVersion: storage.k8s.io/v1
   kind: StorageClass
   metadata:
     name: alicloud-nas-subpath
   mountOptions:
   - nolock,tcp,noresvport
   - vers=3
   parameters:
     volumeAs: subpath
     server: "0cd8b4a576-g****.cn-hangzhou.nas.aliyuncs.com:/k8s/"
   provisioner: nasplugin.csi.alibabacloud.com
   reclaimPolicy: Retain

2. Create the StorageClass:

   kubectl create -f alicloud-nas-subpath.yaml

2. Create a PVC

1. Create pvc.yaml with the following content:

   Parameter	Description	Default
   accessModes	Volume access mode.	ReadWriteMany
   storageClassName	The StorageClass to use.	—
   storage	The requested capacity. This does not limit actual usage unless allowVolumeExpansion: true is set on the StorageClass and the NAS file system is general-purpose. The quota is measured in GiB and rounded up to the nearest integer. For volume expansion, see Expand a dynamically provisioned NAS volume.	—

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

2. Create the PVC:

   kubectl create -f pvc.yaml

3. Deploy applications and verify

This example deploys two nginx applications that share the same NAS subdirectory.

1. nginx-1.yaml

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: deployment-nas-1
     labels:
       app: nginx-1
   spec:
     selector:
       matchLabels:
         app: nginx-1
     template:
       metadata:
         labels:
           app: nginx-1
       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. nginx-2.yaml

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: deployment-nas-2
     labels:
       app: nginx-2
   spec:
     selector:
       matchLabels:
         app: nginx-2
     template:
       metadata:
         labels:
           app: nginx-2
       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

   Both applications reference the same PVC (nas-csi-pvc).

3. Deploy both applications:

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

4. Verify the pods are running:

   • /k8s/: the base path from the StorageClass

   • nas-79438493-f3e0-11e9-bbe5-00163e09****: the automatically created PV name

   kubectl get pod

   Expected output:

   NAME                                READY   STATUS    RESTARTS   AGE
   deployment-nas-1-5b5cdb85f6-a****   1/1     Running   0          32s
   deployment-nas-2-c5bb4746c-b****    1/1     Running   0          32s

   Both pods mount the same NAS subdirectory at /data. The mount target path follows the pattern <mount-target>:/k8s/<pv-name>/:

To mount different subdirectories to different pods, create a separate PVC for each pod.

Use the ACK console

1. Create a StorageClass

1. Log on to the ACK console. In the left-side navigation pane, click ACK consoleClusters.

2. Click the cluster name, then choose Volumes > StorageClasses in the left-side pane.

3. On the StorageClasses page, click Create.

4. Configure the parameters and click Create.

   Parameter	Description	Example
   Name	The StorageClass name. Follow the format requirements displayed in the console.	alicloud-nas-subpath
   PV type	Select NAS.	NAS
   Select mount target	The mount target domain and path. If no mount target exists, create a NAS file system first. See Step 1. To find the domain name, see Manage mount targets.	0cd8b4a576-g****.cn-hangzhou.nas.aliyuncs.com:/k8s/
   Volume mode	Select Subdirectory for subpath mode. Each PVC creates a new subdirectory under the base path. Note Subdirectory mode requires CSI plug-in version 1.31.4 or later. Earlier versions use Shared Directory (sharepath) mode.	Subdirectory
   Mount path	The base path in the NAS file system. If the subdirectory does not exist, it is created automatically. Leave blank to use the root directory. For Extreme NAS, set this to a subdirectory of /share, such as /share/data.	/
   Reclaim policy	Controls what happens to data when a PVC is deleted. Use Retain for high data-security requirements. Important The archiveOnDelete parameter cannot be configured through the console. To delete backend data, use kubectl. In ACK Serverless clusters, the Delete policy does not delete NAS directories because CSI-Provisioner lacks the required Linux privileges.	Retain
   Mount options	NFS mount options. Use NFS v3 (recommended). Extreme NAS supports only NFS v3. See NFS.	(default)

2. Create a PVC

1. In the left-side pane, choose Volumes > Persistent Volume Claims, then click Create.

2. Configure the parameters and click Create.

   Parameter	Description	Example
   PVC type	Select NAS.	NAS
   Name	A unique name for the PVC within the cluster.	pvc-nas
   Allocation mode	Select Use StorageClass.	Use StorageClass
   Existing storage class	Select the StorageClass created in the previous step.	alicloud-nas-subpath
   Capacity	The requested storage capacity. Does not limit actual usage unless directory quotas are enabled. See Expand a dynamically provisioned NAS volume.	20Gi
   Access mode	The volume access mode.	ReadWriteMany

3. Deploy an application

1. In the left-side pane, choose ACK ClustersACK ClustersWorkloads > Deployments, then click Create from Image.

2. Configure the key parameters. Use defaults for all other settings. For full configuration details, see Create a stateless application by using a Deployment.

   Section	Parameter	Description	Example
   Basic information	Name	A custom name for the Deployment.	deployment-nas-1
   	Replicas	Number of pod replicas.	2
   Container	Image name	The container image address.	anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
   	Required resources	vCPU and memory.	0.25 vCores, 512 MiB
   Volume	Add PVC	Select Mount Source (the PVC you created) and Container Path (the mount path in the container).	Mount Source: pvc-nas; Container Path: /data

3. On the Deployments page, click the application name. On the Pods tab, verify the pod is in the Running state.

Use kubectl

1. Create a StorageClass

1. Create alicloud-nas-sharepath.yaml:

   Parameter	Description
   mountOptions	NFS mount options. Use NFS v3 (recommended). Extreme NAS supports only NFS v3. See NFS.
   volumeAs	Set to sharepath.
   server	The mount target and path. All PVs share this path. Replace with your actual mount target. See Manage mount targets.
   provisioner	Must be nasplugin.csi.alibabacloud.com.
   reclaimPolicy	Must be Retain for sharepath mode.

   apiVersion: storage.k8s.io/v1
   kind: StorageClass
   metadata:
     name: alicloud-nas-sharepath
   mountOptions:
   - nolock,tcp,noresvport
   - vers=3
   parameters:
     volumeAs: sharepath
     server: "0cd8b4a576-g****.cn-hangzhou.nas.aliyuncs.com:/data"
   provisioner: nasplugin.csi.alibabacloud.com
   reclaimPolicy: Retain

2. Create the StorageClass:

   kubectl create -f alicloud-nas-sharepath.yaml

2. Create PVCs in different namespaces

1. Create the namespaces:

   kubectl create ns ns1
   kubectl create ns ns2

2. Create pvc.yaml with PVCs in both namespaces:

   In sharepath mode, the storage parameter does not take effect.

   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

3. Deploy applications and verify

1. nginx.yaml

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: nginx
     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
   ---
   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: nginx
     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. Deploy the applications:

   kubectl create -f nginx.yaml

3. Verify the pods are running:

   kubectl get pod -A -l app=nginx

   Expected output:

   NAMESPACE  NAME                    READY   STATUS    RESTARTS   AGE
   ns1        nginx-5b5cdb85f6-a****  1/1     Running   0          32s
   ns2        nginx-c5bb4746c-b****   1/1     Running   0          32s

   Both pods mount 0cd8b4a576-g****.cn-hangzhou.nas.aliyuncs.com:/data at /data, even though they are in different namespaces.

Use the ACK console

1. Create a StorageClass

1. Log on to the ACK console. Click the cluster name, then choose Volumes > StorageClasses.

2. Click Create and configure the parameters.

   Parameter	Description	Example
   Name	The StorageClass name.	alicloud-nas-sharepath
   PV type	Select NAS.	NAS
   Select mount target	The mount target domain and path. See Manage mount targets.	0cd8b4a576-g****.cn-hangzhou.nas.aliyuncs.com:/data
   Volume mode	Select Shared Directory. All PVs share the same NAS path.	Shared Directory
   Mount path	The path within the NAS file system. Leave blank to use the root. For Extreme NAS, use a subdirectory of /share.	/
   Reclaim policy	Must be Retain for sharepath mode.	Retain
   Mount options	NFS mount options. Use NFS v3.	(default)

3. Click Create.

2. Create PVCs in different namespaces

1. Create the ns1 and ns2 namespaces. See Manage namespaces and resource quotas.

2. In the left-side pane, choose Volumes > Persistent Volume Claims. Select ns1 in the Namespace section and click Create.

3. Configure the parameters and click Create.

   Parameter	Description	Example
   PVC type	Select NAS.	NAS
   Name	A unique name within the cluster.	pvc-nas
   Allocation mode	Select Use StorageClass.	Use StorageClass
   Existing storage class	Select the alicloud-nas-sharepath StorageClass.	alicloud-nas-sharepath
   Capacity	The requested capacity (does not take effect in sharepath mode).	20Gi
   Access mode	The volume access mode.	ReadWriteMany

4. Repeat the steps to create pvc-nas in the ns2 namespace.

3. Deploy an application

1. In the left-side pane, choose Workloads > Deployments. Select ns1 in the Namespace section and click Create from Image.

2. Configure the parameters.

   Section	Parameter	Description	Example
   Basic information	Name	Deployment name.	nginx
   	Replicas	Number of replicas.	2
   Container	Image name	Container image.	anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
   	Required resources	vCPU and memory.	0.25 vCores, 512 MiB
   Volume	Add PVC	Mount Source: the PVC in ns1. Container Path: the mount path.	Mount Source: pvc-nas; Container Path: /data

3. Repeat for the ns2 namespace.

4. On the Deployments page, click the application name. On the Pods tab, verify pods are in the Running state.