If they'd got it as right as Heroku then deployment (or CD configuration) would be a one liner once a server is set up and scaling etc. would be configurable via a very simple web console or CLI.
Unless I missed something, last time we tried k8s (admittedly ~6 months ago) it was woefully far from that goal.
Although it didn't come out of the box, my deploys are now one-liners. The command builds, tests and packages my app into a docker image, then bumps the version number on the k8s deployment which triggers a rolling update of production pods. I'm very happy with my current deployment flow, mostly because it works reliability and I can forget about what it's doing under the hood.
Unless I missed something, last time we tried k8s (admittedly ~6 months ago) it was woefully far from that goal.