3 ms·

I am curious, what are the benefits of running kubernetes on your personal servers? Seems like introducing unnecessary complexity.

outworlder 6y ago
You pay upfront for some more components. In exchange, you get a lot of benefits. 'classic' servers are only simpler if you can postpone dealing with their complexity.
- beders 6y ago
  Classic servers are always simpler. Unless you need to manage a whole lot of them. It's like we suddenly have forgotten how to run several services on a single machine. ;)
- kevindong 6y ago
  If you're running on a single-node machine and you don't NEED (or can't have it anyway since you're on a single machine/network/power "cluster") high availability, why bother with K8s over a much simpler vanilla Docker daemon that auto-restarts containers when they crash?
mplewis 6y ago
Kubernetes manages your containers and keeps them up at the scale you want. If you need to scale, you can. If your VPS goes down, you don't care, you just get a new one and plug it in. Your cluster was never down. If you want to move your cluster, you install k8s somewhere else and push the yaml.
- beders 6y ago
  That is wishful thinking at best. If your software doesn't know what to do with the additional compute-power, nothing is going to happen. Your postgresql DB will not automagically scale. Your mail server won't. Your static web server either. Nor your backup software or image server, unless they were specifically made for that. And your bottleneck will still be the disk loading your actual data you want to serve. This should be considered an interesting case study but not a guide on how to actually build your own home servers. And "install k8s somewhere else and push the yaml" doesn't move your data.
  - mplewis 6y ago
    This wasn't a guide on how to build home servers. It was simply a post on how this person uses a tool to manage their home server. Do you have to be so negative about everything?

outworlder 6y ago

You pay upfront for some more components. In exchange, you get a lot of benefits. 'classic' servers are only simpler if you can postpone dealing with their complexity.

beders 6y ago
Classic servers are always simpler. Unless you need to manage a whole lot of them. It's like we suddenly have forgotten how to run several services on a single machine. ;)
kevindong 6y ago
If you're running on a single-node machine and you don't NEED (or can't have it anyway since you're on a single machine/network/power "cluster") high availability, why bother with K8s over a much simpler vanilla Docker daemon that auto-restarts containers when they crash?

mplewis 6y ago

Kubernetes manages your containers and keeps them up at the scale you want. If you need to scale, you can. If your VPS goes down, you don't care, you just get a new one and plug it in. Your cluster was never down. If you want to move your cluster, you install k8s somewhere else and push the yaml.

beders 6y ago
That is wishful thinking at best. If your software doesn't know what to do with the additional compute-power, nothing is going to happen. Your postgresql DB will not automagically scale. Your mail server won't. Your static web server either. Nor your backup software or image server, unless they were specifically made for that. And your bottleneck will still be the disk loading your actual data you want to serve. This should be considered an interesting case study but not a guide on how to actually build your own home servers. And "install k8s somewhere else and push the yaml" doesn't move your data.
- mplewis 6y ago
  This wasn't a guide on how to build home servers. It was simply a post on how this person uses a tool to manage their home server. Do you have to be so negative about everything?