Any chance of packaging this into a CSI for Kubernetes

[wmorgan6796]

I was just curious if there was any way to package this application into a CSI for kubernetes that can be deployable via Helm. I'm looking at using something like this or the AWS S3 CSI (which utilizes mountpoint for S3) but it seems like this can only run on bare-metal?

[Barre]

Hi,

I think you can already already do this through https://github.com/kubernetes-csi/csi-driver-nfs
I've been requested a CSI driver quite a bit. My plan is to implement a VFS interface that can be used as a library from go, and implement a proper CSI driver from there.

[Barre]

VolumeSnapshots and clones could be implemented by snapshotting either zfs or btrfs volumes. I am not sure how to solve it for the filesystem mode.

Snapshots is a feature that I have in plans for ZeroFS

[CounterClops]

Adding my interest to a CSI driver, was looking for a solution I could use with our cloudnative postgres deployments, and came across this. Would love to be able to use our S3 storage as backing for our cold/warm tablespaces, only keeping our recent hot data on our NVMe drives.

[jrcichra]

I made this PoC but haven't been using it for quite a while as I switched to a different method for storing my files (at least, for now). So use at your own risk 😅

[DeanKamali]

I have a local working CSI driver with my fork of ZeroFS. However, I've noticed that formatting the NBD block device with zfs/btrfs/ext4/xfs and re-exporting it via NFS to offer RWX "while functional" degrades performance and is error-prone and flaky compared to using ZeroFS's native NFS.

I think three things need to happen:

1. Native snapshot support with an easy restore path (volume snapshots, create PVC off a snapshot)
2. Redis cache to speed up metadata lookups (recently introduced)
3. Native writeback cache to speed up overall performance

[Barre]

Redis cache to speed up metadata lookups (recently introduced)

The redis stuff that was recently added has nothing to do with performance or caching but is just optionally used to fill the gap with object stores not supporting conditional writes.