3 ms·
I'm sure this has benefit to someone but it doesn't really answer my core "K8S is simple" question in my mind: Single node proxmox VM/LXC mix homeserver. Is le
by Havoc 6y ago
I'm sure this has benefit to someone but it doesn't really answer my core "K8S is simple" question in my mind:
Single node proxmox VM/LXC mix homeserver. Is learning K8S worthwhile?
I can see it helping me on cloud tech (inherently multi node) yet seems like a net negative at home.
It's one of those "it's popular & I could learn that, but what is the personal payoff for me here?"
- tw04 6y ago> Is learning K8S worthwhile? Unless you can use the knowledge for work or just want something you can spend endless hours tweaking/tinkering on, not at all, not even a little bit. It will be less robust and an order of magnitude more difficult to troubleshoot and keep updated. I work on k8s all day long. I welcome some actual responses contrary to my opinion. If he isn’t doing it for knowledge, k8s on a single node is a significant downgrade from proxmox for a home lab. He currently has containers, vms, robust storage, and an extremely easy to use GUI out of the box with proxmox. He gets none of that from k8s without significantly more effort.
- qbasic_forever 6y agoSingle node isn't going to buy you much over a basic docker-compose.yml setup, but IMHO you now have a home 'lab' to experiment and hone your skills. Helm charts, despite their flaws, when done well can be really simple and easy to install and maintain application stacks too. Just a couple CLI commands to get a selfhosted app setup with all of its dependencies like a database, ingress proxy, etc.
- remram 6y agoI find that Kubernetes is more complex than docker-compose, but still has advantages for production deployments. Things like rolling upgrades, config management, versatile services with label selectors (and readiness probes). I have been bitten multiple times by docker-compose reading a variable from my current shell environment instead of an env-file. I'm no fan of Helm though, templating structured files just feels wrong. It clashes a lot with the built-in "valueFrom:" stuff built into Kubernetes; why couldn't Helm use similar "helmVar:" and keep being YAML?
- xyzzy123 6y agoOn a homeserver I think it's a wash, just pick the thing you like best. You can of course run kube inside proxmox if you want to experiment. I think of k8s as being two distinct things. One, it's a way to run and manage software. Two, it's a way to consume software. There are lots of packages out there for k8s (helm charts, pre-made manifests) and so on. If you want to run eg HA gitlab, the "supported" way to do that is on k8s. There are quite a few complex software stacks now where the simplest practical way to set them up is run them in k8s. Most of the time these big beasty things are not what you want to run for home use.
- jvalencia 6y agoI recommend using k3d. I've found running a local instance to be really easy and helpful. Everything you do locally can be transferred to your k8s as a service provider to deploy. (https://k3d.io/ https://k3d.io/)
- cmeacham98 6y ago> Single node proxmox VM/LXC mix homeserver. Is learning K8S worthwhile? Maybe, although if you're fully happy with your current setup then probably not unless you just want to explore and learn new things. I use kubernetes "at home" (ok, well it's an OVH server, but I use it for personal/home stuff), and I like it. I happen to run a wide variety of apps for myself and friends, already used docker, and I was somewhat reaching the limits of docker compose. I really like the consistent ecosystem, and that k8s cleanly deals with problems like TLS termination with LE[1] and automatically updating my DNS[2]. I like that I can just write down what I want in a YAML file and don't have to mess around with docker commands or package managers or what else. It's not for everyone, but I wouldn't say there's no value in it, especially if you're already using containers or a similar tool. 1: https://cert-manager.io/docs/ https://cert-manager.io/docs/ 2: https://github.com/kubernetes-sigs/external-dns https://github.com/kubernetes-sigs/external-dns