On: K3s – Lightweight Kubernetes

[mpsprd]

Can this tool help to simplify self hosting implems? K3s was recommended to me to replace my personal pile of systemd units starting docker compose configs and manual reverse proxy configs.

Im am completely oblivious to how k8s works.

[dewey → mpsprd]

Check out https://kamal-deploy.org, it just hit 1.0 and 37signals moved their whole Kubernetes stack to it. I was playing around with it recently for side projects and I think it's a nice fit for simpler products like that.

[dinosaurdynasty → mpsprd]

systemd units are fine. It's even pretty close to the recommendations for podman.

You can use something like Ansible to make it a bit easier, if that even makes sense in your use case.

[thelastparadise → mpsprd]

People often say kubernetes is complex, or overkill for tasks.

But let's say you have many computers and want to put them to work. Suddenly, kubernetes becomes the simplest of all options.

> Everything should be made as simple as possible, but not simpler.

- Einstein

[packetlost → thelastparadise]

If that's your scenario, fine. But many put themselves in that scenario unnecessarily, which is the real problem.

[dinosaurdynasty → thelastparadise]

Lol no. Docker Swarm, Nomad, even ancient Pacemaker are all simpler and easier to use than k8s. I don't think there's a single feature k8s adds over those options that is actually useful in a non-Enterprise use case (especially homelab stuff, assuming the point of your homelab is not learning k8s).

[ozarker → mpsprd]

I use it for self hosting. It really simplified my reverse proxy config like you said. I use the internal networking between services quite a bit. I have it auto-provisioning volumes on my NAS and using them via NFS. I love it to death and would say it has simplified my setup overall. But the upfront cost of learning k8s is indeed high.

[MrOwen → ozarker]

Seconding this as well. Similar setup (though I opted for longhorn) and journey. I'm very grateful for learning k8s but man, it was definitely rough for a long while until I really understood all the pieces and cemented my understanding. I can very much appreciate that's a tall order for many people and not wanting to embark on that journey unless there's a good reason.

[hhh → mpsprd]

K3s/k8s may help with that, but it's going to be a learning curve. I personally moved onto k8s for a similar reason, but it was a learning curve

[thelastparadise → hhh]

It's a learning curve, but it is consistent, reliable, and standardized.

Kubernetes has become an interface, independent of implementation.

It's much like how POSIX is a standard and there are many implementations.

And yes, POSIX has a learning curve too, but I'd rather learn that than anything proprietary, or non standard/rapidly changing.

[moondev → thelastparadise]

No doubt. The ability to scale is great, but the best thing about Kubernetes is really the API.

[proxysna → mpsprd]

Start with hashicorp nomad. Less of a learning curve and easy to set up. Traefik can do automatic discovery of services in nomad. Definitely better than a bunch of systemd units.