3 ms·
Can anyone tell me when Kubernetes should be used and when it shouldn’t? I’ve been learning about it along with terraform and other devops tools, but Im still
by wara23arish 5y ago
Can anyone tell me when Kubernetes should be used and when it shouldn’t?
I’ve been learning about it along with terraform and other devops tools, but Im still not clear how to identify whether it’s the right tool for the job.
- dreyfan 5y agoKubernetes is like a Rube Goldberg machine. It’s complex to setup, very satisfying to watch in action, and gets the job done even if there’s a few extra moving parts.
- mountainriver 5y agoA bit in places, but it’s all built on very simple primitives
- atomicnumber3 5y agoImo, it's basically all about having software-defined infrastructure. If that's worth it to you, use k8s. If you don't mind just ssh'ing to a box and running docker, or using puppet/ansible or something, that's fine too. I personally like using k8s at work because our dev team is 2000+ people and there's great support for using it in our tooling. I wrote my own thing at home that's basically just a declarative "put this docker container on this host with these options" manager and it's WAY better QOL than when I was using helm and Digital Oceans managed k8s, which is great $ value btw. But Jesus was helm such a pain and at times I was spending more time reading helm and k8s docs than working on my own project. That's my main gripe with k8s. Unlike docker, it is a HuGE surface area to learn, so it takes a lot for that to be worth it.
- nonameiguess 5y agoAre you trying to build a platform (as a service or otherwise) that many developers will deploy many applications into? Strongly consider Kubernetes. Are you trying to deploy one application you're also the developer of? Then use some existing platform as a service unless and until you hit limitations that no commodity offering can overcome and you need to roll your own. Are you trying to deploy a static site or something consisting mostly of informational content that isn't really an application and doesn't have meaningful uptime requirements? Fire and forget some VPS with httpd or nginx serving a directory you update with rsync, or maybe pick some templated off-the-shelf Wordpress thing.