You might not need Kubernetes
Yeah, you probably don&#x27;t. And not only that, but it probably makes your life harder. I&#x27;ve interviewed for a tech lead position at a company working with freelancers and I&#x27;m pretty sure the reason they ended up rejecting me was that I mentioned the technical interviewer that I think containers, container infrastructures (like Kubernetes) and even cloud infrastructure is being overused&#x2F;used without giving too much thought about it as if it came free (in the sense of setup and operating complexity). Too bad the interviewer started rambling about how he was into Kubernetes those days :). (Actually, this was the most technical part of the interview.)<p>I&#x27;m mostly working with startups and small companies creating MVPs and that was their client base too. Now most of the time these are just building CRUD apps, most of the time these apps don&#x27;t see heavy usage for years (maybe never). Developers love technology, love to play with new(ish) things so quite a few of us will prefer using whatever is new and hip for the next project. Now it&#x27;s containers and microservices. And it feels safe, because done right, these will give you scalability. And once you convince the client&#x2F;boss that you need it it&#x27;s unlikely that anyone will come back in a year and say: hey, it seems that we&#x27;ll never need this thing that made the development $X more expensive. (Partly because they won&#x27;t know the amount.) So actually politically it is the safe choice. But professionally and cost wise it&#x27;s usually worse. It&#x27;s a lot better to have to transition after seeing the need (preferably from the projected growth numbers). At least you minimize the expected value of the costs (bacause YAGNI).