30
Kubernetes storage backends (lemmy.world)
submitted 1 year ago by to c/selfhosted@lemmy.world
23 comments fedilink hide all child comments
 

I'm looking for experiences and opinions on kubernetes storage.

I want to create a highly available homelab that spans 3 locations where the pods have a preferred locations but can move if necessary.

I've looked at linstore or seaweedfs/garage with juicefs but I'm not sure how well the performance of those options is across the internet and how well they last in long term operation. Is anyone else hosting k3s across the internet in their homelab?

Edit: fixed wording

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 year ago (4 children)

My gut says go multi cluster (or not) at that pointbut treat the remote as a service, have a local container be a proxy

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 1 year ago (3 children)

    I want the failover to work in case of internet or power outage, not local cluster node failure. Multiple clusters would make configuration and failover across locations difficult or am I wrong?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 1 year ago (2 children)

    I guess i shouldn't have answered, I do have experience with multiple storage-classes, but none of the classes you mention (so like i don't really know anything about them). I envisioned you dealing with pod level storage issues and thought that'd be something most programs would have lots of difficulty dealing with, where as a more service oriented approach would expect remote failures (hence the recommendation).

    All of the things you mentioned don't seem like they have provisioners, so maybe you mean your individual nodes would have these associated remote fs'. At that point i don't think kubelet cares, you just mount those on the machines and tell kubelet about it via host mount

    Oh shit look there's a CSI driver for juicefs https://juicefs.com/docs/csi/introduction/, they kinda start out recommending the host mount https://juicefs.com/docs/cloud/use_juicefs_in_kubernetes/.

    We make some use of PV's but people i find my team often tend to avoid them.

    I probably should have shut my mouth from the start!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 year ago (1 child)

    They both support k8s, juicefs with either just a hostpath (not what i'd use) or the JuiceFS CSI Driver. Linstore has an operator which uses drbd and provides it too.

    If you know of storage classes which are useful for this deployment (or just ones you want to talk about in general) then go on. From what I'm seeing in this thread I'll probably have to deploy all options that seem reasonable and test them myself anyways.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 1 year ago

    For this kind of thing i usually go by popularity (active repo/popular repo), mostly to have the most other people in your boat. It doesn't always work but generally if other users have to migrate at least you can ask them questions.

    On the face of it i'd go with the csi driver version, only because we use alternative csi drivers ourselves, and haven't seen any issues (ours are pretty aws vanella though).

    We use storage classes (for our drivers) the "dynamic provisioning" section of https://juicefs.com/docs/csi/guide/pv, you'll need to make one of those, then create a statefulset and mount the pv in there.

    I do find statefulsets to be a bit of a not as well supported part of kubernetes, but generally they work well enough.

  • permalink
  • fedilink
  • source
  • parent