We have adopted Kubernetes at our startup. It's solved a couple of problems but created a whole lot more. We aren't at the stage that we need the scaling yet.

We evaluated Kubernetes and chose Nomad instead. It works really well (although not as feature rich as K8s) and it allows smaller teams to understand how the whole setup works. It lowers key man risks, IMO.

What problems did it create ?

We adopted Kubernetes at our startup, it solved most ci/cd and devops issues for the team. We didn't need the scaling either, we have at max maybe 2 containers of a service but we know we are ready.

Out of memory issues because we use multiple small machines instead of one big one. There are othrs but we haven't worked out what they are yet.

> This sounds a lot like CV-driven development, rather than any actual use cases.

There are plenty of companies ou there that have old COTS lying around and require some sort of IT infrastructure. Being able to setup and manage a working cluster of COTS hardware is a great way to add computational resources to a company without spending au additional cash or having to rubber stamp permits.

I personally have done this in a previous job, and a small POC with minikube turned into a 3-node kubeadm cluster that deployed and managed two company-wide intranet services like a breeze. Zero cash was spent, the only resource used was a few hours of my time, everyone benefitted, and managers were very happy with the result.

Kubernetes is the 2020's equivalent of "nobody gets fired for buying IBM" of 1980s.

Sort of, but that's only considering the worst possible outcome...

This subthread is about playing with it at home.

Why do you think people write these blog posts.