3 ms·

When people are talking about 50 EUR per month or 100 EUR per month of server expenses, are these problems that do require Kubernetes or is K8s overkill at thes

When people are talking about 50 EUR per month or 100 EUR per month of server expenses, are these problems that do require Kubernetes or is K8s overkill at these levels? A very good friend of mine runs 1400 pods but his company (by that I mean the company he owns) spends something like 10 K EUR / month in servers. It's all Kubernetes and Talos (which another poster mentioned already) etc. But at 50 to 100 EUR per month!? Don't get me wrong: I'm excited to see people using Kubernetes with such low server budgets... I'm into VMs and containers, but haven't tried Kubernetes yet (despite my friend trying hard to convince me it's really not that complicated).

suralind 2mo ago
Setting up Kubernetes (eg with Talos) really is a one-time investment in the sense that you have to figure out what you're doing (what operators to add, how to connect them to they work together, etc.) and is a valuable skill also for work. Of course then there's the maintenance - updating operators, Kubernetes, whatever else you have, but you don't have to do it and if you want to do keep up with recent versions then it's just as much work as on Ubuntu or any other distro. The upside with k8s is that you can definitely roll back (I'm just assuming you're using GitOps). Besides, you'll probably want to add all of that Kubernetes functionality at some point anyway - eg you may just at first deploy your server/app via ClickOps, have some issue, decide GitOps is the way to go, then decide that you really need to have automatic certs, then decide that DB backups would be good to have. With Kubernetes you just keep extending it and never really have to "rethink" the approach cos it's really difficult to shoot yourself in the foot unless you really want to and have a shred of understanding (and to clarify I'm speaking about small deployments), and of course because you're using it yourself your knowledge grows meaning that your expertise grows.
p_l 2mo ago
Kubernetes vastly reduced complexity of running things for me, in part because it sets common patterns, upon which further very usable patterns grow (like the various operators). At this point, I have a 64GB server on Hetzner that has declaratively configured HTTPS with lets encrypt, postgresql databases, storage management, and all of that including running potentially conflicting packages. Could I run it on plain docker? Sure. But I would have to wire it up myself, or deal with various missing pieces. Instead I have k3s where I just need to remember to update the internal certificate once a year.

suralind 2mo ago

Setting up Kubernetes (eg with Talos) really is a one-time investment in the sense that you have to figure out what you're doing (what operators to add, how to connect them to they work together, etc.) and is a valuable skill also for work. Of course then there's the maintenance - updating operators, Kubernetes, whatever else you have, but you don't have to do it and if you want to do keep up with recent versions then it's just as much work as on Ubuntu or any other distro. The upside with k8s is that you can definitely roll back (I'm just assuming you're using GitOps). Besides, you'll probably want to add all of that Kubernetes functionality at some point anyway - eg you may just at first deploy your server/app via ClickOps, have some issue, decide GitOps is the way to go, then decide that you really need to have automatic certs, then decide that DB backups would be good to have. With Kubernetes you just keep extending it and never really have to "rethink" the approach cos it's really difficult to shoot yourself in the foot unless you really want to and have a shred of understanding (and to clarify I'm speaking about small deployments), and of course because you're using it yourself your knowledge grows meaning that your expertise grows.

p_l 2mo ago

Kubernetes vastly reduced complexity of running things for me, in part because it sets common patterns, upon which further very usable patterns grow (like the various operators). At this point, I have a 64GB server on Hetzner that has declaratively configured HTTPS with lets encrypt, postgresql databases, storage management, and all of that including running potentially conflicting packages. Could I run it on plain docker? Sure. But I would have to wire it up myself, or deal with various missing pieces. Instead I have k3s where I just need to remember to update the internal certificate once a year.