English | 简体中文
The FastCFS Container Storage Interface (CSI) Driver provides a CSI interface used by Container Orchestrators to manage the lifecycle of FastCFS volumes.
Status: beta
ExpandCSIVolumes
) is beta since Kubernetes 1.16.Note fastcfs-csi does not supports deletion for static PV.
persistentVolumeReclaimPolicy
in PV spec must be set to Retain
to avoid PV delete attempt in csi-provisioner.
Following sections are Kubernetes specific. If you are Kubernetes user, use followings for driver features, installation steps and examples.
FastCFS CSI Driver | FastCFS Version |
---|---|
v0.4.6-fastcfs5.3.0-1 | v5.3.0 |
v0.4.6-fastcfs5.2.0-1 | v5.2.0 |
v0.4.6-fastcfs5.1.0-1 | v5.1.0 |
v0.4.6-fastcfs5.0.0-1 | v5.0.0 |
v0.4.6-fastcfs4.2.0-1 | v4.2.0 |
v0.4.6-1fastcfs4.1.0 | v4.1.0 |
v0.4.6-3fastcfs4.0.0 | v4.0.0 |
v0.4.6-1fastcfs3.7.1 | v3.7.1 |
v0.4.5 | v3.6.3 |
v0.4.3 | v3.6.0 |
v0.4.2 | v3.5.0 |
v0.4.0 | v3.3.0 |
FastCFS CSI Driver \ Kubernetes Version | v1.17 | v1.18+ |
---|---|---|
master branch | ? | yes |
v0.4.0 | ? | yes |
v2.2.0
or laterauth_enabled = true
--allow-privileged=true
for kubelet
and kube-apiserver
kube-apiserver
feature gates --feature-gates=CSINodeInfo=true,CSIDriverRegistry=true
kubelet
feature gates --feature-gates=CSINodeInfo=true,CSIDriverRegistry=true
The driver requires FastCFS secret to talk to FastCFS to manage the volume on user's behalf. There is a method to grant driver permission:
/etc/fastcfs/auth/keys
) in secret manifest then deploy the secret.curl https://raw.githubusercontent.com/happyfish100/fastcfs-csi/master/deploy/kubernetes/secret.yaml > secret.yaml
# Edit the secret with user credentials
kubectl apply -f secret.yaml
Then reference this key in your storage class.
By default, driver tolerates taint CriticalAddonsOnly
and has tolerationSeconds
configured as 300
, to deploy the driver on any nodes, please set helm Value.node.tolerateAllTaints
to true before deployment
Please see the compatibility matrix above before you deploy the driver
Deploy using kustomization file
kubectl apply -k "github.com/happyfish100/fastcfs-csi/deploy/kubernetes/overlays/dev/?ref=main"
Alternatively, you could also install the driver using helm:
Add the fastcfs-csi Helm repository:
helm repo add fastcfs-csi https://happyfish100.github.io/fastcfs-csi
helm repo update
Then install a release of the driver using the chart
helm upgrade --install fastcfs-csi fastcfs-csi/fcfs-csi-driver
Update FastCFS Config, modify host(data.fdir-cluster.host
, data.fstore-cluster.host
, data.auth-cluster.host
) or more configuration.
For more, see FastCFS Config Example
kubectl edit configmap fastcfs-client-config
kubectl get pods
To view driver debug logs, run the CSI driver with -v=5
command line option
Make sure you follow the Prerequisites before the examples:
Please refer to the matrix in the Kubernetes documentation.
Please go through CSI Spec and General CSI driver development guideline to get some basic understanding of CSI driver before you start.
Dependencies are managed through go module. To build the project, first turn on go mod using export GO111MODULE=on
, then build the project using: make
make test-e2e-single-nn
and make test-e2e-multi-nn
(Now it can only be executed locally, and you can connect to the FastCFS cluster locally)make image-csi
The helm chart for this project is in the charts/fcfs-csi-driver
directory. The manifests for this project are in the deploy/kubernetes
directory. All the manifests except kustomize patches are generated by running helm template
. This keeps the helm chart and the manifests in sync.
When updating the helm chart:
make generate-kustomize
deploy/kubernetes/values
used for generating some manifestsgenerate-kustomize
make target, the deploy/kubernetes/values
files, and the appropriate kustomization.yaml file(s).此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。