this post was submitted on 15 Feb 2026
19 points (100.0% liked)

Selfhosted

56463 readers
955 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
19
k8s storage (CSI) (feddit.it)
submitted 21 hours ago by eutampieri@feddit.it to c/selfhosted@lemmy.world
17 comments fedilink hide all child comments
 

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:

  1. 8 GB RAM, 4 cores VM, control plane. 256 GB SSD
  2. 4 GB RAM, 2 cores, control plane, currently cordoned. 128 GB SSD
  3. 8 GB RAM, 4 cores, ARM, control plane. 512 GB SSD
  4. 8 GB RAM, 4 cores. 256 GB SSD
  5. 16 GB RAM, 6 cores. 256 GB SSD + 1 TB HD
  6. RPi 4, 4 GB RAM. 128 GB SSD
top 17 comments
sorted by: hot top controversial new old
[–] h3ron@lemmy.zip 2 points 15 hours ago* (last edited 15 hours ago) (1 children)

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.

[–] eutampieri@feddit.it 1 points 8 hours ago

Thanks! A bit more involved that I’d have thought but still worth considering! Could you update us after your evaluation?

[–] custard_swollower@lemmy.world 3 points 19 hours ago* (last edited 19 hours ago) (1 children)

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.

[–] eutampieri@feddit.it 1 points 8 hours ago

Which CSI?

[–] supersheep@lemmy.world 4 points 21 hours ago (1 children)

I’m currently using Piraeus / LINSTOR and am quite happy with it: https://github.com/piraeusdatastore/piraeus

[–] eutampieri@feddit.it 2 points 21 hours ago* (last edited 21 hours ago) (2 children)

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?

[–] F04118F@feddit.nl 2 points 16 hours ago (1 children)

Volsync

[–] eutampieri@feddit.it 1 points 8 hours ago

Thanks!

[–] supersheep@lemmy.world 2 points 21 hours ago (1 children)

I can confirm that the resource usage is quite low indeed. I only used it with Nomad instead of Kubernetes, so I can’t comment on how to best migrate PVs and PVCs.

[–] eutampieri@feddit.it 2 points 20 hours ago

Thanks

[–] Decronym@lemmy.decronym.xyz 2 points 19 hours ago* (last edited 8 hours ago)

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

3 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.

[Thread #95 for this comm, first seen 15th Feb 2026, 11:20] [FAQ] [Full list] [Contact] [Source code]

[–] moonpiedumplings@programming.dev 3 points 21 hours ago (2 children)

Openebs mayastor

But you could fit ceph on that I think. As long as your network between nodes is fast enough.

[–] silenium_dev@feddit.org 3 points 20 hours ago

Mayastor or Linstor, Ceph requires too much CPU for these nodes

[–] eutampieri@feddit.it 2 points 21 hours ago

I used to use Ceph at work and I'm a bit reluctant to use it at home. Don’t get me wrong, it’s really cool, but those were beefy nodes, and I only have 1 Gbps between nodes

[–] eutampieri@feddit.it 1 points 21 hours ago (1 children)

Has anyone tried this https://github.com/awslabs/mountpoint-s3-csi-driver?

Perhaps with a Garage DaemonSet as a backend?

[–] jonathan@piefed.social 2 points 19 hours ago* (last edited 19 hours ago) (1 children)

I'd expect the performance to be awful but it still has relatively niche usecases, especially where performance isn't a concern. I'm imagining legacy apps that don't speak S3.

[–] eutampieri@feddit.it 1 points 8 hours ago

Thanks for the feedback! So not what I’m looking for