Container storage interface is an industry standard that enables storage vendors to develop a plugin once and have it work across a number of container orchestration systems.

SeaweedFS is a simple and highly scalable distributed file system, to store and serve billions of files fast!

• Already have a working Kubernetes cluster (includes kubectl)
• Already have a working SeaweedFS cluster

1. Git clone this repository and adjust your SeaweedFS Filer address via variable SEAWEEDFS_FILER in deploy/kubernetes/seaweedfs-csi.yaml (2 places)

2. Apply the container storage interface for SeaweedFS for your cluster. Use the '-pre-1.17' version for any cluster pre kubernetes version 1.17. To generate an up to date manifest from the helm chart, do:

$ helm template seaweedfs ./deploy/helm/seaweedfs-csi-driver > deploy/kubernetes/seaweedfs-csi.yaml

Then apply the manifest.

$ kubectl apply -f deploy/kubernetes/seaweedfs-csi.yaml

3. Ensure all the containers are ready and running

$ kubectl get po -n kube-system

4. Testing: Create a persistant volume claim for 5GiB with name seaweedfs-csi-pvc with storage class seaweedfs-storage. The value, 5Gib does not have any significance as for SeaweedFS the whole filesystem is mounted into the container.

$ kubectl apply -f deploy/kubernetes/sample-seaweedfs-pvc.yaml

5. Verify if the persistant volume claim exists and wait until its the STATUS is Bound

$ kubectl get pvc

6. After its in Bound state, create a sample workload mounting that volume

$ kubectl apply -f deploy/kubernetes/sample-busybox-pod.yaml

7. Verify the storage mount of the busybox pod

$ kubectl exec my-csi-app -- df -h

8. Clean up

$ kubectl delete -f deploy/kubernetes/sample-busybox-pod.yaml
$ kubectl delete -f deploy/kubernetes/sample-seaweedfs-pvc.yaml
$ kubectl delete -f deploy/kubernetes/seaweedfs-csi.yaml

1. Clone project

git clone https://github.com/seaweedfs/seaweedfs-csi-driver.git

2. Install

helm install --set seaweedfsFiler=<filerHost:port> seaweedfs-csi-driver ./seaweedfs-csi-driver/deploy/helm/seaweedfs-csi-driver

3. Clean up

helm uninstall seaweedfs-csi-driver

When update DaemonSet ( DS ) break processes who implements fuse mount. And now new pod not remount net device

For better safe update use node.updateStrategy.type: OnDelete in this need manual update. Steps:

• delete DS pods on node where no exists seaweedfs PV
• cordon or taint node
• evict or delete pods with seaweedfs PV
• delete DS pod on node
• uncordon or remove taint on node
• repeat all steps on [all nodes

By default, driver will create separate folder (/buckets/<volume-id>) and will use separate collection (volume-id) for each request. Sometimes we need to use exact collection name or change replication options. It can be done via creating separate storage class with options:

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: seaweedfs-special
provisioner: seaweedfs-csi-driver
parameters:
  collection: mycollection
  replication: "011"
  diskType: "ssd"

There is another use case when we need to access one folder from different pods with ro/rw access. In this case we do not need additional StorageClass. We need to create PersistentVolume:

apiVersion: v1
kind: PersistentVolume
metadata:
  name: seaweedfs-static
spec:
  accessModes:
  - ReadWriteMany
  capacity:
    storage: 1Gi
  csi:
    driver: seaweedfs-csi-driver
    volumeHandle: dfs-test
    volumeAttributes:
      collection: default
      replication: "011"
      path: /path/to/files
      diskType: "ssd"
    readOnly: true
  persistentVolumeReclaimPolicy: Retain
  volumeMode: Filesystem

and bind PersistentVolumeClaim(s) to it:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: seaweedfs-static
spec:
  storageClassName: ""
  volumeName: seaweedfs-static
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 1Gi

Apache v2 license

Participation in this project is governed by Kubernetes/CNCF code of conduct