Mount a NAS file system to a sandboxed container

How a NAS file system is mounted to a sandboxed container

Examples

The following example describes how to mount a NAS file system to a sandboxed container. In this example, an Apsara File Storage NAS instance is created and a YAML file template is used to create resource objects.

1. Create an Apsara File Storage NAS instance. For more information, see Create a General-purpose NAS file system.
   Notice The NAS file system must be deployed in the same virtual private cloud (VPC) as the cluster.
   Obtain the mount target of the NAS file system. As shown in the following figure, the URL file-system-id.region.nas.aliyuncs.com in the Mount Command column is the mount target.

   Note file-system-id.region.nas.aliyuncs.com is the address of the mount target. You can obtain the address of the mount target in the NAS console. Log on to the NAS console, click the name of the NAS file system. In the left-side navigation pane, click Mounting Usage. You can find the address of the mount target in the Mount Command column.
2. Use the following template to create resource objects:

   cat <<EOF | kubectl create -f -
   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: nas-pvc-csi
     namespace: default
   spec:
     accessModes:
       - ReadWriteMany
     resources:
       requests:
         storage: 5Gi
     selector:
       matchLabels:
         alicloud-pvname: nas-pv-csi
   ---
   apiVersion: v1
   kind: PersistentVolume
   metadata:
     labels:
       alicloud-pvname: nas-pv-csi
     name: nas-pv-csi
   spec:
     accessModes:
       - ReadWriteMany
     capacity:
       storage: 5Gi
     csi:
       driver: nasplugin.csi.alibabacloud.com
       volumeAttributes:
         options: noresvport,nolock
         path: /csi
         server: ${nas-server-address}
         vers: "3"
       volumeHandle: nas-pv-csi
     persistentVolumeReclaimPolicy: Retain
   ---
   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: deploy-nas-csi
   spec:
     replicas: 2
     selector:
       matchLabels:
         app: busybox
     template:
       metadata:
         labels:
           app: busybox
         annotations:
           storage.alibabacloud.com/enable_nas_passthrough: "true"
       spec:
         runtimeClassName: runv
         containers:
           - name: busybox
             image: registry.cn-hangzhou.aliyuncs.com/acs/busybox:v1.29.2
             command: 
             - tail
             - -f
             - /dev/null
             volumeMounts:
               - name: nas-pvc
                 mountPath: "/data"
         restartPolicy: Always
         volumes:
           - name: nas-pvc
             persistentVolumeClaim:
               claimName: nas-pvc-csi
   EOF

   Note

   • Replace ${nas-server-address} in the template with the address of the mount target.

     server: ${nas-server-address}

   • By default, pods cannot communicate with NAS file systems. You must add an annotation in the template to enable the pod to communicate with the NAS file system.

     annotations:
             storage.alibabacloud.com/enable_nas_passthrough: "true"

3. Run the following commands to query the ID of the pod and query the type of the file system that is mounted to the pod:

   kubectl get pods

   kubectl exec -it ${podid} sh

   mount | grep /data | grep nfs

   If the output is not empty, it indicates that the NAS file system is mounted to the container.