Container Service for Kubernetes:Configure a shared NAS volume

Mount the NAS file system

1. Log on to the NAS console. In the left navigation pane, choose File System > File System List.

2. In the top navigation bar, select the resource group and region where your file system resides.

   

3. Find the file system you created and click Mount in the Actions column.

   The first time you use the mount feature, NAS prompts you to assign the AliyunServiceRoleForNasEcsHandler service-linked role. Follow the on-screen instructions to complete the authorization. For details, see Service-linked roles of NAS.

4. In the Mount panel, configure the mount settings:

   1. Select a mount target and click Next.

   2. Select an ECS instance and click Next. The ECS instance must be in the same VPC as the file system. If you cannot find the instance in the list, refresh the page and try again. > Note: To mount a NAS file system on multiple ECS instances at once, see Mount an NFS file system on multiple ECS instances at a time.

   3. Configure the mount parameters:

      Parameter	Description	Required	Default
      Mount path	The local directory on the ECS instance where the file system will be mounted.	Yes	—
      Automatic mount	When enabled, the file system remounts automatically when the ECS instance restarts.	No	Enabled
      Protocol type	The NFS protocol version. General-purpose NAS supports NFSv3 and NFSv4; Extreme NAS supports NFSv3 only. Use NFSv3 for optimal performance when multiple ECS instances do not need to write to the same file simultaneously.	Yes	—
      NAS directory	The directory in the NAS file system to mount. Enter / for the root directory or a subdirectory such as /abc. If the directory does not exist, select Confirm New Directory — you must also set the UID, GID, and POSIX permissions for the new directory.	No	/ (root)
      Mount parameters	NFS mount flags. For the full parameter reference, see Mount an NFS file system on a Linux ECS instance.	No	Default mount parameters

5. Click Complete. The mount operation takes about 1 to 2 minutes. When the mount status shows Mounted, the NAS file system is ready. If the status shows Failed, use the built-in troubleshooting tool. For guidance, see Mount an NFS file system on a Linux ECS instance.

   

Verify the mount

Connect to the ECS instance and run the following commands to confirm the file system is accessible:

mkdir /mnt/dir1
mkdir /mnt/dir2
touch /mnt/file1
echo 'some file content' > /mnt/file2
ls /mnt

The output lists dir1, dir2, file1, and file2:

To view mount details or check the file system capacity, run mount -l or df -h.

Each NAS file system requires a mount target to connect to an ECS instance. To add mount targets or look up existing mount target addresses, see Manage mount targets. When adding a mount target, set Mount target type to VPC and select the same VPC and vSwitch as your ACK cluster.

Create a PV

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

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

3. On the Persistent Volumes page, click Create. Configure the parameters in the dialog box and click OK.

   Parameter	Description	Required	Default	Example
   PV type	Select NAS.	Yes	—	NAS
   Name	A unique name for the PV within the cluster.	Yes	—	pv-nas
   Capacity	Used only for PVC matching — it does not cap the actual usable storage. The actual storage limit is determined by the NAS file system specifications. For details, see General-purpose NAS file systems and Extreme NAS file systems.	Yes	—	5 Gi
   Access mode	ReadWriteMany lets multiple nodes mount the volume as read-write simultaneously. ReadWriteOnce restricts mounting to a single node.	Yes	—	ReadWriteMany
   Enable CNFS	Whether to use Container Network File System (CNFS) for automated O&M, cache acceleration, and performance monitoring. To manage an existing NAS file system with CNFS, see Create a CNFS to manage a NAS file system (Recommended).	No	Disabled	Disabled
   Mount target domain name	Available only when CNFS is disabled. The address of the NAS mount target. Select from previously added mount targets, or enter a custom domain name. To look up the address, see Manage mount targets.	Yes (when CNFS is disabled)	—	0c47****-mpk25.cn-shenzhen.nas.aliyuncs.co
   Mount path (Advanced)	The subdirectory of the NAS file system to mount. For Extreme NAS, the path must start with /share (for example, /share/data). If the directory does not exist, it is created automatically.	No	/ (root)	/data
   Reclaim policy	Retain (default): when the PVC is deleted, the PV and NAS data are preserved and must be cleaned up manually. Delete: must be used with archiveOnDelete. Static PVs do not support archiveOnDelete, so the PV and data are not deleted even with this policy set. For archiveOnDelete configuration, see Use dynamically provisioned NAS volumes.	No	Retain	Retain
   Mount options	The NFS protocol version and mount flags. NFSv3 delivers better performance for ML training workloads where multiple clients read from the same dataset without concurrent writes.	No	—	nolock,tcp,noresvport<br>vers=3
   Label	Labels to attach to the PV.	No	—	pv-nas

After the PV is created, it appears on the Persistent Volumes page.

Create a PVC

1. In the navigation pane, choose Storage > Persistent Volume Claims.

2. On the Persistent Volume Claims page, click Create. Configure the parameters and click OK.

   Parameter	Description	Required	Default	Example
   PVC type	Select NAS.	Yes	—	NAS
   Name	A unique name for the PVC within the cluster.	Yes	—	pvc-nas
   Allocation mode	Select Use Existing Persistent Volume to bind to the PV created above. Alternatively, select Create Volume to provision a new PV inline.	Yes	—	Use Existing Persistent Volume
   Existing volumes	Select the PV created in the previous step.	Yes (when using existing PV)	—	pv-nas
   Capacity	The storage capacity to claim. Used only for PVC-to-PV matching and does not limit actual usable capacity.	Yes	—	5

Verify the PV and PVC

After creating the PVC, confirm it is bound to the PV. Connect to any node in the ACK cluster and run:

kubectl get pvc pvc-nas

The output shows the PVC in Bound state:

NAME       STATUS   VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
pvc-nas    Bound    pv-nas   5Gi        RWX                           1m

If the status is Pending, check that the PV name in the PVC matches exactly and that the access modes are compatible.