the problem with container on a single box is that you still need to solve a bunch of problems thay k8s solves for you with that. By the time you've handled dep

the problem with container on a single box is that you still need to solve a bunch of problems thay k8s solves for you with that. By the time you've handled deploying updated containers, a sidecar for logging and/or metrics, service discovery, and decided you _maybe_ want two instances of your app, you likely should have just used k8s from the get go. You get all of that straight out of the box, and it's going to be much easier to hire someone to manage that than the mess of bash scripts you end up with otherwise.