It really, really wants a higher-level abstraction layer over the top of it. I can see how you'd build something heroku-like with it, but exposing app developers to it just seems cruel.

> I can see how you'd build something heroku-like with it

That's what many teams end up half-arsing without realising they're attempting to build a PaaS.

They adopt K8S thinking it's almost 90% a PaaS. It's not.

They continue hiring, building a DevOps team just to handle K8S infrastructure things, then a Platform team to build the PaaS on top of it.

Then because so many people have jobs, nobody at this point wants to make an argument that perhaps using an actual PaaS might make sense. Not to mention "the sunk cost" of the DIY PaaS.

Then on top of that, realising they've built a platform mostly designed for microservices, everything then must become a microservice. 'Monolith' is a banned word.

Argh

Thing is, k8s is already an abstraction layer on top of something like AWS or GCP