Comment by linkdd

Situation A:

  We've built our infrastructure on top of docker-compose on a single node server
  We've grown enough so that we need more servers and now k8s seems like a good fit
  Uh oh, we need to rewrite everything or not use k8s and reinvent the wheel

Situation B:

  We've deployed a single node k8s cluster and built our infrastructure on top of it
  We've grown enough so that we need more servers
  Good, just need to migrate to the new cluster, no need to rewrite anything

> I wish it would go away completely

Ain't gonna happen, because Docker Compose is only about running containers, there is no:

  - secret management
  - network policies
  - container scheduling with node affinity etc...
  - storage management
  - extensibility with other k8s operators (hello cert-manager, kubedb, kubevault, tekton, kubirds, etc...)
  - ...

I love how HN hates k8s for no valid reason.