File Storage NAS:Mount NAS file systems on ACS

Step 1: Obtain NAS file system information

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

   Note

   The following steps describe how to obtain the information in 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 and obtain the VPC ID and vSwitch ID used by pods 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 left navigation bar, choose Configuration Management > > ConfigMaps.

   4. On the ConfigMaps page, change the namespace at the top to kube-system, find acs-profile, and click Edit YAML.

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

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

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

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

      • NAS file systems cannot be mounted across VPCs, which means they cannot be used across regions. Make sure that the region of the existing NAS file system is the same as that of the ACS cluster.

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

      • Verify that the protocol type of the NAS file system is NFS. You cannot mount NAS file systems that use the SMB protocol.

      

   3. Verify that the mount target meets the requirements and obtain the mount target address.

      1. Click the file system ID.

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

      3. In the Mount Target section, verify that the existing mount target meets the requirements, and then obtain the mount target address.

         Note

         • The system automatically creates a mount target for a General-purpose NAS file system. However, you need to manually create mount targets for Extreme NAS file systems.

         • If the existing mount target does not meet the requirements, you can 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 pods in the ACS cluster. Otherwise, the mounting will fail.

         • It is recommended that the vSwitch of the mount target is the same as the vSwitch used by pods in the ACS cluster for better performance.

         • 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. Create a file named nas-sc.yaml and copy the following template into the file. Modify the parameters in the template as required.

   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 in the template.

   Important

   NAS file systems of different types and storage specifications support different regions and zones. Specify the region, zone, virtual private cloud (VPC), and vSwitch of the NAS file system and mount target that you want to create based on the storage requirements of your business, the region of the ACS cluster, and the VPC and vSwitch that are used by pods in the ACS 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 and Extreme NAS.

   • General-purpose NAS file systems and Extreme NAS file systems have different limits on mounting connectivity, the number of file systems, and file sharing protocols. 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 and obtain the VPC ID and vSwitch ID used by pods 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. extreme: Extreme NAS file system. For more information, see Extreme NAS.
   storageType	The storage type of the NAS file system. For General-purpose NAS file systems, the following values are supported: Performance (default): Performance Capacity: Capacity For Extreme NAS file systems, the following values are supported: standard (default): medium advanced: advanced
   regionId	The ID of the region to which the NAS file system belongs. The region ID must be the same as that of the ACS cluster.
   zoneId	The ID of the zone to which the NAS file system belongs. Select a zone based on the vSwitch used by the pod in the ACS cluster. Note Within the same VPC, a NAS file system can be mounted across zones. We recommend that you select the same zone for better performance.
   vpcId, vSwitchId	The IDs of the VPC and the vSwitch to which the mount target of the NAS file system belongs. Set the values to the IDs of VPC and vSwitch used by pods in the ACS cluster.
   accessGroupName	The permission group to which the mount target of the NAS file system belongs. The default value is DEFAULT_VPC_GROUP_NAME.
   provisioner	The driver type. Set the value to nasplugin.csi.alibabacloud.com, which indicates that the Alibaba Cloud NAS CSI plugin is used.
   reclaimPolicy	The reclaim policy of the PV. Only Retain is supported. This value indicates that the NAS file system and its mount target are retained when the PV is deleted.

2. Create a StorageClass.

   kubectl create -f nas-sc.yaml

3. Check 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 YAML 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

   Field description:

   Parameter	Description
   accessModes	The access mode.
   storage	The storage capacity allocated to the pod. This is also the capacity of the NAS volume that you want to create. Note Because Extreme NAS file systems have a minimum capacity limit of 100 GiB, if the NAS file system type defined in the StorageClass is Extreme NAS, the value of storage must be greater than or equal to 100 GiB. Otherwise, the corresponding PV cannot be created.
   storageClassName	The name of the StorageClass that you want to associate.

2. Create a PVC.

   kubectl create -f nas-pvc-fs.yaml

3. View the PVC.

   kubectl get pvc

   A command output similar to the following one is returned. The PVC is associated with the PV that is automatically created. 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 and add the following content to the file:

   The following YAML template creates a Deployment that provisions two pods. Both pods request storage resources through a PVC named nas-pvc-fs and mount the NAS volume to the /data directory.

   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 a Deployment and mount the NAS file system.

   kubectl create -f nas-test-fs.yaml

3. Check the status of the pods created by 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. View the mount path.

   Run the following command to view files in the mount path. By default, no data is returned.

   kubectl exec nas-test-****-***a -- ls /data