kubernetes-csi-tencentcloud/deploy/cfsturbo/kubernetes/ directory and upload csi-node-rbac.yaml, csi-node.yaml, and csidriver-new.yaml files to the kubectl management node.kubernetes-csi-tencentcloud/deploy/cfsturbo/examples/ directory and download the pv.yaml, pvc.yaml, and pod.yaml sample files.pv.yaml, pvc.yaml, and pod.yaml files based on the PV, PVC, and Pod attributes, such as name and image address.
Below are the sample YAML files:apiVersion: v1kind: PersistentVolumemetadata:name: csi-cfsturbo-pvspec:accessModes:- ReadWriteManycapacity:storage: 10Gicsi:driver: com.tencent.cloud.csi.cfsturbo# volumeHandle in PV must be unique, use pv name is bettervolumeHandle: csi-cfsturbo-pvvolumeAttributes:# cfs turbo protoproto: lustre# cfs turbo rootdirrootdir: /cfs# cfs turbo fsid (not cfs id)fsid: d3dcc487# cfs turbo server iphost: 10.0.1.16# cfs turbo subPathpath: /storageClassName: ""---apiVersion: v1kind: PersistentVolumeClaimmetadata:name: csi-cfsturbo-pvcspec:accessModes:- ReadWriteManyresources:requests:storage: 10Gi# You can specify the pv name manually or just let Kubernetes bind the pv and pvc.volumeName: csi-cfsturbo-pv# cfsturbo only supports static provisioning, the StorageClass name should be empty.storageClassName: ""---apiVersion: apps/v1kind: Deploymentmetadata:labels:k8s-app: csi-cfsturbo-podname: csi-cfsturbo-podspec:replicas: 1selector:matchLabels:k8s-app: csi-cfsturbo-podtemplate:metadata:labels:k8s-app: csi-cfsturbo-podspec:containers:- image: nginxname: csi-cfsturbo-podvolumeMounts:- mountPath: /csi-cfsturboname: csi-cfsturbovolumes:- name: csi-cfsturbopersistentVolumeClaim:# Replaced by your pvc name.claimName: csi-cfsturbo-pvc
sudo mount.lustre -o sync,user_xattr 10.0.1.16@tcp0:/d3dcc487/cfs /path/to/mount
fsid is not the CFSID, and you need to enter the information in the mount directory.kubectl apply -f csi-node-rbac.yaml && kubectl apply -f csidriver-new.yaml && kubectl apply -f csi-node.yaml
kubectl create -f pv.yaml && kubectl create -f pvc.yaml && kubectl create -f pod.yaml
kubectl get pod -n default -o wide

STATUS is ContainerCreating, the creation failed. You can view the failure reason based on the events in the TKE console.Feedback