3 ms·
I can agree that the idea of reaching for Kubernetes to set up a bunch of services on a home server sounds a bit absurd. "How did we get here?" I'm not an ine
by gavinray 6y ago
I can agree that the idea of reaching for Kubernetes to set up a bunch of services on a home server sounds a bit absurd.
"How did we get here?"
I'm not an inexperienced codemonkey by any means of the term, but I am a shitty Sysadmin. And despite being a Linux user from early teens, I'm not a greybeard.
As sorry a state as it may sound, I have more faith in my ability to reliably run and maintain a dozen containers in k8s than a dozen standard, manually installed apps + processes managed by systemd.
Whether this is a good thing or a bad thing you can likely find solid arguments both ways for.
- henryfjordan 6y agoYou only have to learn 1 interface (albeit a complicated one) to use Docker/k8s compared with 1 interface per service to run them manually.
- klodolph 6y agoHm, these days I feel like I only have to learn systemd. Reload config? View logs? Watchdog? Namespaces? It’s all systemd. If you are running on one machine, what does Docker/k8s give you that you do not already have?
- nineteen999 6y ago> If you are running on one machine, what does Docker/k8s give you that you do not already have? That feeling that you are part of a special, futuristic club.
- vineyardmike 6y agoNothing, but its pretty common to have the home server plus a desktop/laptop where you do most of the work (even for home server), that may not be linux - in which case containers are the easiest way