Hello selfhosted !

Continuing my journey of setup up my home k3s cluster.

I’ve been asking myself if Longhorn might be overkill for my home cluster,here’s what i did:

3 machines running k3s each. One of them has a storage in Raid 5 and I dont want to use any storage from the other two.

Thing is, i had to configure replicas to 1 in longhorn for my pv to be green.

Hence my question, since data is already replicated in the array, shouldn’t I just use a NFS storage class instead?

Thanks !

  • cygnus@lemmy.caEnglish
    5·
    1 year ago

    I’ve never heard of this particular “Longhorn” and was very confused as to why Windows Vista was coming up in conversation.

  • citizen@sh.itjust.worksEnglish
    2·
    1 year ago

    Sounds like NFS is a way to go in your case. Longhorn adds for your setup unnecessary resource overhead and complexity.

  • Starbuck@lemmy.worldEnglish
    2·
    1 year ago

    Longhorn is basically just acting like a fancy NFS mount in this configuration. It’s a really fancy NFS mount that will work well with kubernetes, for things like PVC resizing and snapshots, but longhorn isn’t really stretching its legs in this scenario.

    I’d say leave it, because it’s already setup. And someday you might add more (non-RAID) disks to those other nodes, in which case you can set Longhorn to replicas=2 and get some better availability.

  • magikmw@lemm.eeEnglish
    1·
    1 year ago

    Longhorn isn’t just about replication (which is not backup, and RAID is not backup either). Also if you only have one replica, is it even different from local storage at this point?

    You’d use longhorn to make sure applications don’t choke and die when the storage they are using go down. Also, I’m not sure if you can supply longhorn storage to nodes that don’t run it. I haven’t tried it.

    I suspect all pods that you’d define to use longhorn would only go up at the longhorn replica node.

    All this is how I understand longhorn works. I haven’t tried it this way, my only experience is running it on every node so if one node goes down pods can just restart on any other node and carry on.