I’m currently using Piraeus / LINSTOR and am quite happy with it: https://github.com/piraeusdatastore/piraeus
post
replies:
Openebs mayastor
But you could fit ceph on that I think. As long as your network between nodes is fast enough.
replies:
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| NFS | Network File System, a Unix-based file-sharing protocol known for performance and efficiency |
| SSD | Solid State Drive mass storage |
| k8s | Kubernetes container management package |
[Thread #95 for this comm, first seen 15th Feb 2026, 11:20] [FAQ] [Full list] [Contact] [Source code]
replies:
I’m not sure you’ll get nice performance in local network with small appliances (consumer network hardware, mini PCs and rpi 4). I’ve never got sub-ms network disk access on 1Gbps switch and router. In the end I’ve done the opposite - I’ve added one k8s host with a lot of storage, and any storage services are deployed there. All the other k8s services rely on local SSDs.
replies:
I have two storage nodes and one is much faster than the other.
I'm currently evaluating a juicefs deployment based on two minio instances (one per node, replicated with async bucket replication) through a load balancer (sidekick) in failover. Because juicefs also needs a db for metadata, I went with valkey + sentinel.
Juicefs provides a CSI driver that supports ReadWriteMany volumes and CSI snapshots and manages both read and write cache. Performance is much much better than Ceph. In theory it should be riskier (because of the async replication) but in practice I haven't yet lost a bit.
replies:
Has anyone tried this https://github.com/awslabs/mountpoint-s3-csi-driver?
Perhaps with a Garage DaemonSet as a backend?
replies:
all 20 comments