Container Service for Kubernetes:Mount NAS via EFC client with CNFS

Step 1: Create a CNFS resource

This section shows how to configure an existing NAS file system to use the EFC client. To create a new NAS file system through CNFS with EFC, add useClient: EFCClient in the parameters section when creating the ContainerNetworkFileSystem resource. See Use CNFS to manage NAS file systems (recommended) for details.

1. Save the following YAML as cnfs-efc.yaml.

   Parameter	Description
   description	A description for the file system.
   type	The volume type. Set to nas for NAS file systems.
   reclaimPolicy	Only Retain is supported. Deleting the CNFS resource does not delete the underlying NAS file system.
   server	The mount target address. The mount target must be in the same VPC as your pods and its status must be Ready. For best performance, use the same vSwitch for both the mount target and pods. If no existing mount target meets these requirements, create a new one.
   useClient	Set to EFCClient to enable the EFC client.

   apiVersion: storage.alibabacloud.com/v1beta1
   kind: ContainerNetworkFileSystem
   metadata:
     name: cnfs-efc-test
   spec:
     description: "cnfs"
     type: nas
     reclaimPolicy: Retain
     parameters:
       server: 17f7e4****-h****.cn-beijing.nas.aliyuncs.com
       useClient: EFCClient

2. Create the CNFS resource:

   kubectl create -f cnfs-efc.yaml

Step 2: Create a PersistentVolume and PersistentVolumeClaim

Save the following YAML as cnfs-pv-pvc.yaml.

apiVersion: v1
kind: PersistentVolume
metadata:
  name: efc-pv
spec:
  accessModes:
  - ReadWriteMany
  capacity:
    storage: 50Gi
  claimRef:
    name: efc-pvc
    namespace: default
  csi:
    driver: nasplugin.csi.alibabacloud.com
    volumeAttributes:
      containerNetworkFileSystem: cnfs-efc-test
      path: /
    volumeHandle: efc-pv
  volumeMode: Filesystem
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: efc-pvc
  namespace: default
spec:
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 50Gi
  storageClassName: ""
  volumeMode: Filesystem
  volumeName: efc-pv

Apply the configuration:

kubectl create -f cnfs-pv-pvc.yaml

Step 1: Create a Deployment

Save the following YAML as cnfs-deployment.yaml.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: efc-test
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: efc-test
  template:
    metadata:
      labels:
        app: efc-test
    spec:
      containers:
      - command:
        - sh
        - -c
        - |
          sleep infinity
        image: alibaba-cloud-linux-3-registry.cn-hangzhou.cr.aliyuncs.com/alinux3/alinux3:latest
        name: test
        volumeMounts:
        - mountPath: /mnt
          name: pvc
      volumes:
      - name: pvc
        persistentVolumeClaim:
          claimName: efc-pvc

Apply the configuration:

kubectl create -f cnfs-deployment.yaml

Step 2: Verify the EFC mount

1. Check that the pod is running:

   kubectl get pod -l app=efc-test

   Expected output:

   NAME                       READY   STATUS    RESTARTS   AGE
   efc-test-f545b86d6-spr7p   1/1     Running   0          29m

2. Once the pod reaches the Running state, confirm the EFC mount point inside the pod:

   kubectl exec <pod-name> -- mount -t fuse.aliyun-alinas-efc

   Expected output:

   bindroot-3889a-8TzEY5mc:3d2804****-w****.cn-shanghai.nas.aliyuncs.com:/ on /mnt type fuse.aliyun-alinas-efc (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=1048576)

   The mount type fuse.aliyun-alinas-efc confirms EFC is active. If the output shows nfs instead, the node does not meet the OS or kernel requirements and has fallen back to the NFS protocol. Check the node OS version and kernel version against the prerequisites.