If I were going to build out bare-metal k8s, I would first try Swarm instead. I would not use k3s or an alternative. The biggest problem with k8s (any version of it) is its overall cost in expertise and maintenance is incredibly high (if you're doing it right; many people are completely ignorant to how terribly they're maintaining it and assume their cost is low). Swarm's cost is going to be significantly smaller, both in the short and long term.

▲

horsawlarway 6 months ago | parent | next [-]

Can you speak more precisely about what costs you think something like k3s imposes that are solved by swarm?

Right now this comment has the same kind of FUD that I see in the swarm docs (there is no "why" to swarm in the docker published docs that feels particularly compelling, especially given the amount of time and energy docker seems to be putting into their k8s tooling instead).

I'm willing to bite - but I run a baremetal cluster on k3s, and it's very simple to keep up to date.

	▲	nwienert 6 months ago \| parent [-]
		Not the parent but I had a Kubernetes setup I migrated to Swarm a few years back. I don't remember a most details honestly, but I do remember deleting so much configuration (and duplicate config with my local compose), and generally finding it much easier to work with. I even had a couple machines set up without much trouble as it was all built-in. But I'm not an infra person and my k8s experience is minimal.

▲

conradfr 6 months ago | parent | prev [-]

That's what CapRover uses.