Selfhosted

61385 readers

278 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Kubernetes storage backends (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by InnerScientist@lemmy.world 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

[–] InnerScientist@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

Thanks for the info!

I'll try Rook-Ceph, Ceph has been recommended quite a lot now, but my nvme drives sadly don't have PLP. Afaict that should still work because not all nodes will face power loss at the same time.

I'd rather start with the hardware I have and upgrade as necessary, backups are always running for emergency cases and I can't afford to replace all hard drives.

I'll join Home Operations and see what infos I can find

[–] F04118F@feddit.nl 2 points 1 year ago

The problem with non-PLP drives is that Rook-Ceph will insist that its writes get done in a way that is safe wrt power loss.

For regular consumer drives, that means it has to wait for the cache to be flushed, which takes aaaages (milliseconds!!) and that can cause all kinds of issues. PLP drives have a cache that is safe in the event of power loss, and thus Rook-Ceph is happy to write to cache and consider the operation done.

Again, 1Gb network is not a big deal, not using PLP drives could cause issues.

If you don't need volsync and don't need ReadWriteMany, just use Longhorn with its builtin backup system and call it a day.