You don't need k8s, containers, and multiple cloud instances to automate deployment.
It's perfectly possible and simple to implement a button to deploy on a single machine.
Heck, on OVH or Hetzner, you can have a dedicated bare metal machine with many cores and RAM exclusive to you, cheaper than famous cloud instances. These bare metals will handle what takes sometimes hundreds of containers to handle, with a much simple and easy to maintain infra.
Nothing about K8 or containers are light... they are buckets where bad devs hide the bodies in most cases.
You could but why all the extra overhead?
Libcontaier lxc all use the same api calls to the kernel... so in effect your still correct (mostly)
They all have overhead, if you're starting to use their features... cgroups can have some very funny impacts on app performance more so if your running containers ontop of a linux install over a hypervisor vs nix on hardware.
Do you see how many extra steps that is.
If you need isolation for multiple services, just use a container... I don't see an orchestration need that justifies using k8s on a single machine. For such context, it's too much hassle for very little value in return.
Not just cheaper, fixed cost.
Everyone who cried about exit fees on AWS needed the lesson of failing to plan ahead...
This isn’t any better than Joe sysadmin and could be worse since the complexity is higher and there’s a greater chance to do more damage with one change. Adding complexity makes bad process worse.
Maybe clicking a button that sshes into the box and runs git pull?