Container Compute Service:Use NAS volumes

Step 1: Get NAS file system information

1. Obtain the VPC ID and vSwitch ID used by the ACS pods.

   Note

   The following steps describe how to obtain the information from the console. You can also run the kubectl get cm -n kube-system acs-profile -o yaml command to view the YAML file of acs-profile. Obtain the VPC ID and vSwitch ID from the vpcId and vSwitchIds fields.

   1. Log on to the ACS console.

   2. On the Clusters, click the name of the cluster to go to the cluster management page.

   3. In the navigation pane on the left, choose Configurations > ConfigMaps.

   4. At the top of the ConfigMaps page, set the namespace to kube-system. Then, find acs-profile and click Edit YAML.

   5. Obtain the VPC ID and vSwitch ID from the vpcId and vSwitchIds fields.

2. Confirm that the existing NAS file system meets the requirements and obtain the mount target address.

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

   2. Find the target NAS file system. Confirm that its region, zone, and protocol type meet the requirements.

      • NAS file systems cannot be mounted across VPCs and therefore cannot be used across regions. Make sure the region of the NAS file system is the same as that of the ACS cluster.

      • In the same VPC, a NAS file system can be mounted across zones. However, for better performance, use a NAS file system in the same zone as the pods in the ACS cluster.

      • Confirm that the NAS file system uses the NFS protocol. You cannot mount NAS file systems that use the SMB protocol.

      

   3. Confirm that the mount target meets the requirements and obtain its address.

      1. Click the file system ID.

      2. In the navigation pane on the left of the file system details page, click Mount Targets.

      3. In the Mount Target area, confirm that the existing mount target meets your requirements and obtain the mount target address.

         Note

         • A mount target is automatically created for a General-purpose NAS file system. You must manually create mount targets for Extreme NAS file systems.

         • If the existing mount target does not meet the requirements, create a new one. For more information, see Manage mount targets.

         • The VPC of the mount target must be the same as the VPC used by the pods in the ACS cluster. Otherwise, the mount fails.

         • For better performance, the vSwitch of the mount target should be the same as the vSwitch used by the pods in the ACS cluster.

         • The status of the mount target is Available.

         

Step 2: Create a PVC

Step 3: Create an application and mount the NAS volume

Step 1: Create a StorageClass

1. Modify the following YAML content based on the parameter descriptions and save it as a file named nas-sc.yaml.

   apiVersion: storage.k8s.io/v1
   kind: StorageClass
   metadata:
     name: alicloud-nas-fs
   mountOptions:
   - nolock,tcp,noresvport
   - vers=3
   parameters:
     volumeAs: filesystem
     fileSystemType: standard
     storageType: Performance
     regionId: cn-shanghai
     zoneId: cn-shanghai-e
     vpcId: "vpc-2ze2fxn6popm8c2mzm****"
     vSwitchId: "vsw-2zwdg25a2b4y5juy****"
     accessGroupName: DEFAULT_VPC_GROUP_NAME
     deleteVolume: "false"
   provisioner: nasplugin.csi.alibabacloud.com
   reclaimPolicy: Retain

   The following table describes the parameters.

   Important

   Different types and storage classes of NAS file systems are supported in different regions and zones. You must select an appropriate region, zone, VPC, and vSwitch for the NAS file system and mount target. The selection must be compatible with the region of your ACS cluster and the VPC and vSwitch information of the pods in the cluster. For more information, see the following topics:

   • For information about the storage specifications, performance, billing, and supported regions and zones of different types of NAS file systems, see General-purpose NAS file systems and Extreme NAS file systems.

   • General-purpose NAS file systems and Extreme NAS file systems have different limits on mount connectivity, the number of file systems, and protocol types. For more information, see Limits.

   • You can run the kubectl get cm -n kube-system acs-profile -o yaml command to view the YAML file of acs-profile. Retrieve the VPC ID and vSwitch ID from the vpcId and vSwitchIds fields.

   Parameter	Description
   volumeAs	Only filesystem is supported. This value indicates that a NAS file system is automatically created. Each NAS volume corresponds to a NAS file system.
   fileSystemType	The type of the NAS file system. standard (default): General-purpose NAS file system. For more information, see General-purpose NAS file systems. extreme: Extreme NAS file system. For more information, see Extreme NAS file systems.
   storageType	The storage class of the NAS file system. For General-purpose NAS file systems, the following values are supported: Performance (default): compute-optimized instance Capacity: storage-optimized For Extreme NAS file systems, the following values are supported: standard (default): medium advanced: advanced
   regionId	The ID of the region where the NAS file system resides. The region ID must be the same as that of the ACS cluster.
   zoneId	The ID of the zone where the NAS file system resides. Select a zone based on the vSwitch used by the pod in the ACS cluster. Note In the same VPC, a NAS file system can be mounted across zones. For better performance, we recommend that you select the same zone.
   vpcId, vSwitchId	The IDs of the VPC and vSwitch where the mount target of the NAS file system resides. Set these to the IDs of the VPC and vSwitch used by the pods in the ACS cluster.
   accessGroupName	The permission group of the mount target of the NAS file system. The default value is DEFAULT_VPC_GROUP_NAME.
   provisioner	The driver type. This must be set to nasplugin.csi.alibabacloud.com, which indicates that the Alibaba Cloud NAS Container Storage Interface (CSI) plug-in is used.
   reclaimPolicy	The reclaim policy of the PV. Currently, only Retain is supported. This means that when the PV is deleted, the corresponding NAS file system and mount target are retained.

2. Create the StorageClass.

   kubectl create -f nas-sc.yaml

3. View the StorageClass.

   kubectl get sc

   Expected output:

   NAME                             PROVISIONER                       RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
   alicloud-nas-fs                  nasplugin.csi.alibabacloud.com    Retain          Immediate              false                  13m
   ......

Step 2: Create a PVC

1. Save the following content as a file named nas-pvc-fs.yaml.

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

   The following table describes the parameters.

   Parameter	Description
   accessModes	The access mode.
   storage	The storage capacity to allocate to the pod. This is the capacity of the NAS volume to create. Note Extreme NAS file systems have a minimum capacity of 100 GiB. If the NAS file system type defined in the StorageClass is Extreme NAS, the value of storage must be 100 GiB or greater. Otherwise, the corresponding PV cannot be created.
   storageClassName	The name of the StorageClass to bind.

2. Create the PVC.

   kubectl create -f nas-pvc-fs.yaml

3. View the PVC.

   kubectl get pvc

   The output shows that the PVC is associated with the automatically created PersistentVolume (PV). You can go to the NAS console to view the corresponding NAS file system.

   NAME         STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      VOLUMEATTRIBUTESCLASS  AGE
   nas-pvc-fs   Bound    nas-04a730ba-010d-4fb1-9043-476d8c38****   20Gi       RWX            alicloud-nas-fs   <unset>                14s

Step 3: Create an application and mount the NAS volume

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

   The following YAML file creates a deployment that contains two pods. Both pods request storage from the PVC named nas-pvc-fs and mount the volume to the /data path.

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: nas-test
     labels:
       app: nginx
   spec:
     replicas: 2
     selector:
       matchLabels:
         app: nginx
     template:
       metadata:
         labels:
           app: nginx
       spec:
         containers:
         - name: nginx
           image: registry.cn-hangzhou.aliyuncs.com/acs-sample/nginx:latest
           ports:
           - containerPort: 80
           volumeMounts:
             - name: pvc-nas
               mountPath: /data
         volumes:
           - name: pvc-nas
             persistentVolumeClaim:
               claimName: nas-pvc-fs

2. Create the deployment and mount the NAS volume.

   kubectl create -f nas-test-fs.yaml

3. Check the status of the pods in the deployment.

   kubectl get pod | grep nas-test

   The following output shows that two pods are created.

   nas-test-****-***a   1/1     Running   0          40s
   nas-test-****-***b   1/1     Running   0          40s

4. Check the mount path.

   kubectl exec nas-test-****-***a -- df -h /data

   Expected output:

   Filesystem                                        Size  Used Avail Use% Mounted on
   350514*****-mw***.cn-shanghai.nas.aliyuncs.com:/   10P     0   10P   0% /data

   If a similar output is returned, the file system is mounted.

Step 1: Get NAS file system information

For more information about how to obtain the NAS mount target address, see Obtain NAS file system information.

Step 2: Create an application and mount the NAS volume

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

   The following YAML creates a deployment with two pods. Both pods mount the NAS file system to the /data path using a volume named nfs-nas.

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: nas-test
     labels:
       app: nginx
   spec:
     replicas: 2
     selector:
       matchLabels:
         app: nginx
     template:
       metadata:
         labels:
           app: nginx
       spec:
         containers:
         - name: nginx
           image: registry.cn-hangzhou.aliyuncs.com/acs-sample/nginx:latest
           ports:
           - containerPort: 80
           volumeMounts:
             - name: nfs-nas
               mountPath: /data
         volumes:
         - name: nfs-nas
           nfs:
             server: file-system-id.region.nas.aliyuncs.com    # The mount target address of the Alibaba Cloud NAS file system. Replace this with your actual value. Example: 7bexxxxxx-xxxx.ap-southeast-1.nas.aliyuncs.com.
             path: /    # The path of the directory in the NAS file system. The directory must be an existing directory or the root directory. The root directory for a General-purpose NAS file system is "/". The root directory for an Extreme NAS file system is "/share".

2. Create the deployment and mount the NAS volume.

   kubectl create -f nas-test-nfs.yaml

3. Check the status of the pods in the deployment.

   kubectl get pod | grep nas-test

   The following output shows that two pods are created.

   nas-test-****-***a   1/1     Running   0          40s
   nas-test-****-***b   1/1     Running   0          40s

4. Check the mount path.

   kubectl exec nas-test-****-***a -- df -h /data

   Expected output:

   Filesystem                                        Size  Used Avail Use% Mounted on
   350514*****-mw***.cn-shanghai.nas.aliyuncs.com:/   10P     0   10P   0% /data

   If a similar output is returned, the file system is mounted.