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?

  • mnemonicmonkeys@sh.itjust.worksOP
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    12 hours 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