Hacker News Reader

> I can spin up effectively identical dev/ci/stg/prod clusters for a new project in an hour for a medium sized project, with CD in addition to everything GP mentioned.

I can do the same thing with `make local` invoking a few bash commands. If the complexity increases beyond that, a mistake has been made.

You could say the same thing about Ansible or Vagrant or Nomad or Salt or anything else.

I can say with complete confidence however, that if you are running Kubernetes and not thinking about ops, you are simply not operating it yourself. You are paying someone else to think about it for you. Which is fine, but says nothing about the technology.

You always have to think about ops, regardless of tooling. I agree that you can have a very nice, reproducible setup with any of those tools though. Personally, I haven't found those alternatives to be significantly easier to use (though I don't have experience with Salt).

For me personally, self hosted k3s on Hetzner with FluxCD is the least painful option I've found.

Managed k8s is great if you already in the cloud, selfhosting it as a small company is waste of money.

I've found self hosted k3s to be about the same effort as EKS for my workloads, and maybe 20-30% of the cost for similar capability.