Even if using just one VM, I'll probably slap k3s on it and manage my application using manifests. It's just so much easier than dealing with puppet or chef or vanilla cloud-init. Docker compose works too, but at that point it's just easier to stick with k3s and then I can have nice things like background jobs, a straightforward path to HA, access to an ecosystem of existing software, and a nicer CLI.

▲

tayo42 3 hours ago | parent [-]

Thats what I don't get when people bring up this idea k8s is complicated.

All of those other tools are complicated and fragile

	▲	throwaway894345 an hour ago \| parent [-]
		I think the things that trip people up are: 1. People expect k8s to be an opinionated platform and it's very happy to let you make a mess 2. People think k8s is supposed to be a cross platform portability layer and ... it maybe can be if you're very careful, but it's mostly not that 3. People compare k8s/cloud/etc to some monolithic application with admin permissions to everything and they compare that to the "difficulty" of dealing with RBAC/IAM/networking/secrets management 4. People don't realize how much more complicated vanilla Linux tooling and how much more accidental complexity is involved