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

Selfhosted

60093 readers
805 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.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

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

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
23
k8s storage (CSI) (feddit.it)
submitted 4 months ago by eutampieri@feddit.it to c/selfhosted@lemmy.world
25 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
you are viewing a single comment's thread
view the rest of the comments
[–] eutampieri@feddit.it 1 points 4 months ago (1 children)

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

[–] h3ron@lemmy.zip 2 points 4 months ago

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.