I work with Kubernetes quite a bit, so I'm reasonably knowledgable on the pro's and con's. I definitely think there is a misunderstanding about what Kubernetes

I work with Kubernetes quite a bit, so I'm reasonably knowledgable on the pro's and con's. I definitely think there is a misunderstanding about what Kubernetes solves. I think Kubernetes is very good at helping structure very large applications where a split of micro-services makes sense. Most start-ups don't need it - it's likely overkill, and unless you go with a vendor you're likely to set it up incorrectly. But it is an advantage in much larger, spread out teams if the culture surrounding all the teams makes sense. If sub-teams can handle their applications really well, which many companies have achieved, then it does provide significant benefits over monoliths. I think the problem you're noticing is that everyone wants to jump onto Kubernetes without realizing why it's even there - the same with micro-services. I shudder when I hear that from my friends with no more than 10 people on their development team, but I think it makes a lot more sense when I see teams of >200 complaining that their huge monolith is what causes the most friction.