> All I’m saying is: Choose your weapons carefully. That's the right moral of the story to take away. > Today, I’m back with a single machine that handles the

> All I’m saying is: Choose your weapons carefully. That's the right moral of the story to take away. > Today, I’m back with a single machine that handles the peak 500 concurrent users And this is what tells me k8s is probably not the right tool for the job. Something that runs on a single machine should absolutely run on a single machine... Unless if there's a pre-existing, funded and operated cluster you can tap into. No abstraction comes for free, as the author mentioned you need to figure routing, backup, etc. You are paying a premium for the fact that you want to make that somewhat generic enough to fit with multiple use cases. The abstraction doesn't materialize for the operator of the cluster. It's there for the customers of that cluster - the devs who can now avoid to configure whatever the cluster is already handling.