Container Service for Kubernetes:Mount a statically provisioned NAS volume

Mount a statically provisioned NAS volume in the ACK console

Step 1: Create a PV

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

2. On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose Volumes > Persistent Volumes.

3. In the upper-right corner of the Persistent Volumes page, click Create.

4. In the Create PV dialog box, configure the following parameters.

   Parameter	Description
   PV Type	You can select Cloud Disk, NAS, or OSS. In this example, NAS is selected.
   Volume Name	The name of the PV that you want to create. The name must be unique in the cluster. In this example, pv-nas is used.
   Capacity	The capacity of the PV. A NAS file system provides unlimited capacity. This parameter does not limit the storage usage of the NAS file system but defines the capacity of the PV.
   Access Mode	You can select ReadWriteMany or ReadWriteOnce. Default value: ReadWriteMany.
   Enable CNFS	Specify whether to enable Container Network File System (CNFS). After you enable CNFS, you must perform the following operations: Select the corresponding CNFS or create a new CNFS. For more information about CNFS, see Use CNFS to manage NAS file systems (recommended). You can specify whether to enable CNFS acceleration. For more information about CNFS acceleration, see Enable the distributed caching feature of the CNFS client.
   Mount Target Domain Name	You can select Select Mount Target to select a mount target or select Custom to enter a mount target. For more information about how to view the domain name of a mount target, see View the domain name of a mount target.
   Show Advanced Options	Mount Path: The mount path of the NAS file system. The mount path must start with a forward slash (/), which indicates the root directory. After you set this parameter, the PV is mounted to the specified subdirectory. If the specified subdirectory does not exist, the system automatically creates the subdirectory in the NAS file system and mounts the subdirectory to the cluster. If you do not set this parameter, the root directory of the NAS file system is mounted. If you want to mount an Extreme NAS file system, the subdirectory must be under the /share directory. Reclaim Policy: This parameter is set to Delete by default. You can also set this parameter to Retain. Delete: If the reclaim policy is deleted, you must configure the archiveOnDelete parameter. If you set archiveOnDelete to true, the related PV and NAS file system are renamed after you delete a PVC. They are not deleted together with the PVC. If you set archiveOnDelete to false, the related PV and NAS file system are also deleted when you delete a PVC. Retain: When a PVC is deleted, the related PV and NAS file system are retained and can only be manually deleted. If you require higher data security, we recommend that you use the Retain mode to prevent data loss caused by user errors. Mount Options: The optional parameters for mounting a NAS file system, including the version of the NFS protocol. We recommend that you use NFSv3. Extreme NAS file systems support only NFSv3. For more information about the NFS protocol, see NFS.
   Label	Add labels to the PV.

5. After you complete the configuration, click Create.

Step 2: Create a PVC

1. In the left-side navigation pane of the details page, choose Volumes > Persistent Volume Claims.

2. In the upper-right corner of the Persistent Volume Claims page, click Create.

3. In the Create PVC dialog box, set the following parameters.

   Parameter	Description
   PVC Type	You can select Cloud Disk, NAS, or OSS. In this example, NAS is selected.
   Name	The name of the PVC. The name must be unique in the cluster.
   Allocation Mode	In this example, Existing Volumes is selected. Note If no PV is created, you can set Allocation Mode to Create Volume and set the required parameters to create a PV. For more information, see Step 1: Create a PV.
   Existing Storage Class	Click Select PV. Find the PV that you want to use and click Select in the Actions column.
   Capacity	The capacity of the PV. Note The capacity claimed by the PVC cannot exceed the capacity of the PV that is bound to the PVC.
   Access Mode	The default value is ReadWriteMany. You can also set the value to ReadWriteOnce or ReadOnlyMany.

4. Click Create.

   After the PVC is created, you can view the PVC in the PVCs list. The PVC is bound to the corresponding PV.

Step 3: Create an application

1. In the left-side navigation pane of the details page, choose Workloads > Deployments.

2. On the Deployments page, click Create from Image.

3. Configure the application parameters.

This example shows how to configure the volume parameters. For more information about other parameters, see Create a stateless application by using a Deployment.

You can add local volumes and cloud volumes.

• Add Local Storage: You can select HostPath, ConfigMap, Secret, or EmptyDir from the PV Type drop-down list. Then, set the Mount Source and Container Path parameters to mount the volume to a container path. For more information, see Volumes.

• Add PVC: You can add cloud volumes.

In this example, a NAS volume is mounted to the /tmp path in the container.

4. After the application configuration is completed, click Create.

Mount a statically provisioned NAS volume by using kubectl

Statically provisioned NAS volumes

1. Create a statically provisioned PV.

   1. Create a file named pv-nas.yaml and copy the following content into the file:

      apiVersion: v1
      kind: PersistentVolume
      metadata:
        name: pv-nas
        labels:
          alicloud-pvname: pv-nas
      spec:
        capacity:
          storage: 5Gi
        accessModes:
          - ReadWriteMany
        csi:
          driver: nasplugin.csi.alibabacloud.com
          volumeHandle: pv-nas   # Specify the name of the PV. 
          volumeAttributes:
            server: "2564f4****-ysu87.cn-shenzhen.nas.aliyuncs.com"
            path: "/csi"
        mountOptions:
        - nolock,tcp,noresvport
        - vers=3

      Parameter	Description
      name	The name of the PV.
      labels	The labels that you want to add to the PV.
      storage	The capacity of the NAS volume.
      accessModes	The access mode of the PV. The default value is ReadWriteMany. You can also set the value to ReadWriteOnce or ReadOnlyMany.
      driver	The type of the storage driver that is used to provision the volume. In this example, the parameter is set to nasplugin.csi.alibabacloud.com. This indicates that the CSI plug-in provided by Alibaba Cloud is used.
      volumeHandle	The unique identifier of the PV. Enter the name of the PV. If multiple PVs are used, the identifier of each PV must be unique.
      server	The mount target of the NAS file system. Important Replace the value with the domain name of a mount target. For more information about how to view the domain name of a mount target, see View the domain name of a mount target.
      path	The subdirectory of the NAS file system that you want to mount. If you want to mount an Extreme NAS file system, the subdirectory must be under the /share directory.
      vers	The version of the NFS protocol. We recommend that you use NFSv3. Extreme NAS file systems support only NFSv3. For more information about the NFS protocol, see NFS.

   2. Run the following command to create a statically provisioned PV:

      kubectl create -f pv-nas.yaml

2. When you create a PVC of the NAS type, set the selector parameter to specify how to select a PV and bind it to the PVC.

   1. Create a file named pvc-nas.yaml and copy the following content into the file:

      kind: PersistentVolumeClaim
      apiVersion: v1
      metadata:
        name: pvc-nas
      spec:
        accessModes:
          - ReadWriteMany
        resources:
          requests:
            storage: 5Gi
        selector:
          matchLabels:
            alicloud-pvname: pv-nas

      Parameter	Description
      name	The name of the PVC.
      accessModes	The access mode of the PV. The default value is ReadWriteMany. You can also set the value to ReadWriteOnce or ReadOnlyMany.
      storage	The capacity claimed by the PVC. The claimed capacity cannot exceed the capacity of the PV that is bound to the PVC.
      matchLabels	The labels are used to select a PV and bind it to the PVC.

   2. Run the following command to create a PVC used for static provisioning:

      kubectl create -f pvc-nas.yaml

3. Deploy an application named nas-static and associate the PVC with the application.

   1. The following YAML template provides an example of the nas.yaml file that is used to create the nas-static application.

      apiVersion: apps/v1
      kind: Deployment
      metadata:
        name: nas-static
        labels:
          app: nginx
      spec:
        replicas: 2
        selector:
          matchLabels:
            app: nginx
        template:
          metadata:
            labels:
              app: nginx
          spec:
            containers:
            - name: nginx
              image: nginx
              ports:
              - containerPort: 80
              volumeMounts:
                - name: pvc-nas
                  mountPath: "/data"
            volumes:
              - name: pvc-nas
                persistentVolumeClaim:
                  claimName: pvc-nas

      Parameter	Description
      mountPath	The path of the container to which the NAS volume is mounted.
      claimName	The name of the PVC that is mounted to the application.

   2. Run the following command to create an application named nas-static and mount the created PVC to the application:

      kubectl create -f nas.yaml

4. Run the following command to query the pods that run the application:

   kubectl get pod

   Expected output:

   NAME                          READY   STATUS    RESTARTS   AGE
   nas-static-5b5cdb85f6-n****   1/1     Running   0          32s
   nas-static-c5bb4746c-4****    1/1     Running   0          32s