Except it was created to model virtually every solution to every compute need. It’s not about the compute itself, it’s about the taxonomy, composability, and verifiability of specifications which makes Kubernetes excellent substrate for nearly any computing model from the most static to the most dynamic. You find kubernetes everywhere because of how flexible it is to meet different domains. It’s the next major revolution in systems computing since Unix.
I (roughly) believe this as well[0], but more flexibility generally means more complexity. Right now, if you don't need the flexibility that k8s offers, it's probably better to use a solution with less flexibility and therefore less complexity. Maybe in a decade if k8s has eaten the world there'll be simple k8s-based solutions to most problems, but right now that's not always the case
[0] I think that in the same way that operating systems abstract physical hardware, memory management, process management, etc, k8s abstracts storage, network, compute resources, etc
Always two extremes to any debate. I've personally enjoyed my journey with it. I've even been in an anti-k8s company running bare metal on the Hashi stack (won't be running back to that anytime soon). I think the two categories I've seen work best are either something lik ECS or serverless and Kubernetes.
