Feature | Involved Object | Involved Operation Permission |
Supporting dynamic creation/deletion of cfsturbo subdirectory type pv | persistentvolumeclaims/persistentvolumes/storageclasses | get/list/watch/create/delete/update |
| node | get/list/ |
kind: ClusterRoleapiVersion: rbac.authorization.k8s.io/v1metadata:name: cfsturbo-csi-controller-rolerules:- apiGroups: [""]resources: ["persistentvolumes"]verbs: ["get", "list", "watch", "create", "delete", "update"]- apiGroups: [""]resources: ["persistentvolumeclaims"]verbs: ["get", "list", "watch", "update"]- apiGroups: [""]resources: ["nodes"]verbs: ["get", "list"]- apiGroups: [""]resources: ["events"]verbs: ["get", "list", "watch", "create", "update", "patch"]- apiGroups: ["storage.k8s.io"]resources: ["storageclasses"]verbs: ["get", "list", "watch"]
Configuration Item | Description |
Name | Enter the StorageClass name. |
Region | It is the region of the cluster by default. |
Provisioner | Select Cloud File Storage CFS Turbo here. |
CFS Turbo | Please select the already created CFS Turbo. If you do not have a suitable CFS Turbo, please go to the Cloud File Storage console to create a new one. For details, see Creating File Systems and Mount Targets. |
Reclaim Policy | Two reclaim policies are provided: Delete and Retain. For data security, it is recommended to use the Retain reclaim policy. Delete: If a PV is dynamically created through a PVC, the PV and storage instance bound to the PVC will be automatically terminated when the PVC is terminated. Retain: If a PV is dynamically created through a PVC, the PV and storage instance bound to the PVC will be retained when the PVC is terminated. |
Configuration Item | Description |
Name | Enter the name of the PersistentVolumeClaim. |
Namespace | A namespace is used to assign cluster resources. Select default here. |
Provisioner | Select Cloud File Storage CFS Turbo. |
Read/Write Permission | CFS only supports multi-server read and write. |
Specify StorageClass or Not | Select Specify. Note: The PVC and PV will be bound to the same StorageClass. Do not specify implies that the StorageClass value of this PVC will be empty, corresponding to a void value under the storageClassName field in the YAML file as a character string. |
StorageClass | Choose the StorageClass created in the steps above. |
Specify a PersistentVolume or Not | Specify the PersistentVolume according to demand.
Note: The system first searches the current cluster for PVs that meet the binding rules. If there are no such PVs, the system dynamically creates a PV to be bound based on the PVC and StorageClass parameters. Either the StorageClass or PersistVolume should be specified. For more details on Not Specifying PersistVolume, see PV and PVC Binding Rules. |
Configuration Item | Description |
Source Setting | Select Static Creation. |
Name | Enter the name of the PersistentVolume. |
Provisioner | Select Cloud File Storage CFS Turbo. |
Read/Write Permission | CFS only supports multi-server read and write. |
Specify StorageClass or Not | Select Do not specify. |
CFS Turbo | Please select the created CFS Turbo. If you do not have a suitable CFS Turbo, please go to the Cloud File Storage console to create a new one. For details, see Creating File Systems and Mount Targets. |
CFS Turbo Root Directory | Fill in according to the root directory of the mount point information in CFS Turbo. |
CFS Turbo Subdirectory | Fill in according to the subdirectory of the mount point information in CFS Turbo. |
Configuration Item | Description |
Name | Enter the name of the PersistentVolumeClaim. |
Namespace | A namespace is used to assign cluster resources. Select default here. |
Provisioner | Select Cloud File Storage CFS Turbo. |
Read/Write Permission | CFS only supports multi-server read and write. |
Specify StorageClass or Not | Select Do not specify. Note: The PVC and PV will be bound to the same StorageClass. Do not specify implies that the StorageClass value of this PVC will be empty, corresponding to a void value under the storageClassName field in the YAML file as a character string. |
StorageClass | Choose the StorageClass created in the steps above. |
Specify a PersistentVolume or Not | Specify the PersistentVolume according to demand.
Note: The system first searches the current cluster for PVs that meet the binding rules. If there are no such PVs, the system dynamically creates a PV to be bound based on the PVC and StorageClass parameters. Either the StorageClass or PersistVolume should be specified. For details on Not Specifying PersistVolume, see PV and PVC Binding Rules. |
Was this page helpful?