k8s storage (CSI)
from eutampieri@feddit.it to selfhosted@lemmy.world on 15 Feb 00:34
https://feddit.it/post/26790529
from eutampieri@feddit.it to selfhosted@lemmy.world on 15 Feb 00:34
https://feddit.it/post/26790529
I’m looking for storage classes for a multi node cluster. I’m currently using Longhorn and NFS, but I’m not happy with the performance. My cluster doesn’t have beefy nodes, so Ceph/Rook is out of the question (for now).
Nodes:
- 8 GB RAM, 4 cores VM, control plane. 256 GB SSD
- 4 GB RAM, 2 cores, control plane, currently cordoned. 128 GB SSD
- 8 GB RAM, 4 cores, ARM, control plane. 512 GB SSD
- 8 GB RAM, 4 cores. 256 GB SSD
- 16 GB RAM, 6 cores. 256 GB SSD + 1 TB HD
- RPi 4, 4 GB RAM. 128 GB SSD
threaded - newest
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.
Thanks! A bit more involved that I’d have thought but still worth considering! Could you update us after your evaluation?
Well actually it is very easy to spin up in docker and most of the configuration happens through env variables.
juicefs itself only exists on the client side, so you basically only have to install and configure the CSI driver with helm.
as it took me a few days to come up with this solution I’d be happy to share my config files.
Performance wise is quite fast on sequential reads (it saturates my 2.5G bandwidth) and slower than I expected on sequential writes (for me it caps at 60MB/s). Postgresql seems happy. I saw no visible performance degradation with Authentic, Immich and Opencloud. Nextcloud installation took ages. I’ve yet to try it with jellyfish and the *arr suite.
A simple NFS share would be faster, but it doesn’t support replication, failover and CSI snapshots.
I’m currently using Piraeus / LINSTOR and am quite happy with it: github.com/piraeusdatastore/piraeus
Found a Reddit thread that says that LINSTOR has a lower CPU usage (which is my main gripe with Longhorn). Might as well try this and report back. Is there a good way to migrate PVs and PVCs?
It’s great, I spent 2 years finding perfect CSI for homelab and landed on Piraeus. The best part is you get full read performance of your local disk so I didn’t have to use 10G, write are limited by network link between nodes. But that hasn’t been a problem for me. Also, they’re super responsive for any issues/bugs you hit.
Let me know if you have any specific questions about this.
Thanks, I will!
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
[Thread #95 for this comm, first seen 15th Feb 2026, 11:20] [FAQ] [Full list] [Contact] [Source code]
I started setting up longhorn today. My hardware is a little it beefier, but I still am curious: what performance problems did you run into exactly?
My greatest problem is that the CPU load is too high and I ran into an issue with iSCSI that would occasionally peg one core to 100%. It would also make nodes NotReady when too many PVs were scheduled
What CPUs are you running exactly? I was under the assumption my greatest bottleneck would be an 1Gbps LAN
Just don’t go below 4 cores of x86 and you’ll be fine