The "your" part of that is the problem. Other people are not in a position to know what my requirements are, so telling me what my app does or doesn't need comes off as arrogant. The anti-k8s crowd always talks as though the only reason anyone would choose k8s is that they're brainwashed by the hype. It's never possible that a team actually weighed all of their constraints and made a rational choice.

> The anti-k8s crowd always talks as though the only reason anyone would choose k8s is that they're brainwashed by the hype

Maybe, but the pro-k8s camp always assumes everyone is building microservices or web services that need to scale.

If all you want to do is to scale, you can just use auto scaling with prebaked VM images on the cloud or whatever.

K8s really shines when what you want to do is to optimize usage of your resources (I'd argue especially when running on bare metal)