Hacker News new | ask | show | jobs
by geerlingguy 2949 days ago
IMO, only if you're working on like 100+ of them. If you just maintain a website using a traditional LAMP/LEMP stack, Rails, Node.js, or something like that it still makes more sense (unless you want to be 'trendy') to stick to primitives or use more managed hosting.

But if you're maintaining a fleet of independent sites, Kubernetes' scheduling can make sense, despite the inherent complexity (TBH, you're going to have a similar level of complexity managing the same kind of scale with any other tool).

1 comments

K8s also makes sense if you have more than a single server. it's not as easy to keep all your servers up to date, without some automation.
You don't need K8s to automate maintenance of a small number of servers.