external-snapshotter VS csi-driver-smb

By the way, I got that error very often - kubernetes-csi/external-snapshotter#300 - the fix is in progress. I'm afraid about the snapshot mechanism performance. It's also a question about the GCP snapshot mechanism, so I'm gathering opinions.

VolSync is a much better option than Velero IMO, Velero was created before GitOps was a thing and it really tries to do too much when all I need is a reliable way to backup and restore PVCs. If your CSI supports volume snapshots, VolSync can use the snapshot-controller to create Volume Snapshots and then mount those as a PVC to a temporary pod to then backup that up to S3. This is really great for backing up PVCs because it's not backing them up from a running workload.

Is it required to store it to s3? If I were U i would use native approach https://kubernetes.io/docs/concepts/storage/volume-snapshots/ with https://github.com/kubernetes-csi/external-snapshotter

#Install CSI Snapshotter and CRDs kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshotcontents.yaml kubectl apply -n kube-system -f https://github.com/kubernetes-csi/external-snapshotter/raw/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshotclasses.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshots.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/deploy/kubernetes/snapshot-controller/setup-snapshot-controller.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/deploy/kubernetes/snapshot-controller/rbac-snapshot-controller.yaml

https://github.com/kubernetes-csi/csi-driver-smb. This is the CSI driver we use.

Actual media storage (movies, pictures, anything that lives on my unRAID box) is mounted to each pod that needs it via the SMB CSI driver. I would love to use NFS instead, but even with 4.x, I was running into stale file mount issues. You can see my findings and why I decided to use SMB instead here

What is the recommended way to use S3 as shared storage for media (videos)? Currently I'm using SAMBA network share RWX volumes using this plugin and I would like to switch to S3 compatible service to increase performance and to avoid my current limit set by my cloud provider on that SAMBA server of 10 active connections for SAMBA.

With SMB I'm using the CSI SMB Driver helm chart to deploy it. When creating the persistent volume I'm able to use some mounting options where I have the following included:

Kubernetes has a native solution for many different storage integrations - CSI. There is a CSI driver for SMB as well. After installing the driver you will be able to map your config files from smb server via regular volume mount and config map.

I mean, in short either find a project that includes support for it (I don't know of one), or look at a CSI that does like the SMB CSI driver.

Using a CSI Plugin you should be able to separate the admin side from the user side. I haven't dove into this but here is a plugin that might help - https://github.com/kubernetes-csi/csi-driver-smb

Look into using flex volumes (though depricated) or its successor SMB CSI driver