Man, compose can be so much simpler for local dev though, you can easily bind local files and you don't need a fancy setup for local dev. We just switched from docker compose to k8s so that it was closer to prod, but I think if we had to do it again I'm not sure I'd bother.
With Skaffold, you can bind (or rather transparently sync) local files to a Pod.
I agree the initial setup is more difficult with a K8s local dev than with a Docker Compose local dev.
But the impedance mismatch makes using Docker Compose a bad idea when you deploy to a K8s cluster.
The secrets management is different. The way pods talk to each other is different. App-level configuration and updates are different. There is so much that diverges, that you end up with two independent systems. One for dev and one for prod. This is not good.
And use Skaffold or Tilt to manage it all.
This setup makes Docker Compose look like a toy.
Developers should stop with this impedence mismatch of using Docker Compose when developing and K8s in prod.