this post was submitted on 08 Oct 2025
52 points (83.3% liked)

Selfhosted

61647 readers
572 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

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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.

  8. 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:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I've been kicking around the idea of running a server for games and chat woth some of my friends, but worry about everyone getting cut off when there's a disruption.

I've started looking into kubernetes out of curiosity, and it seems like we could potentially set up a cluster with master nodes at 3+ locations to hose whatever game server or chat server that we want with 100% uptime, solving my concerns.

Am I misunderstanding the kubernetes documentation, and this is just a terrible idea? Or am I on the right track?

you are viewing a single comment's thread
view the rest of the comments
[–] mnemonicmonkeys@sh.itjust.works 0 points 10 months ago

100% uptime is really not feasible so forget that. Even the commercial servers have downtimes.

What I was thinking of doing was having 2-3 separate boxes distributed between houses and could automatically switch which boxes handles resources when 1 goes down. No individual box would have 100% uptime, but you'd have minimal disruptions when any particular box has issues or needs maintenance.

Unfortunately, it doesn't seem like kubernetes works that way, and I don't know of any software that would. Best bet now is probably to distribute backups between the boxes and manually spin up a secondary box when the primary goes down