Whilst procrastinating doing the personal project coding that I intended to do (why!?), I spent my precious off-baby-duty minutes last night bringing up a #k3s #RaspberryPi cluster ( https://k3s.io/ )
I had intended to limit control plane traffic to just these nodes, but I already had a #firewalld zone setup to constrain traffic to local sources, and traffic can only match one source-based zone
That firewall configuration part aside, the rest of the cluster setup was effortless
This time around, I want to give seaweedfs ( https://github.com/seaweedfs/seaweedfs ) a try for high-availability storage, which will hopefully unblock me in terms of actually doing useful things on my #selfhosted #kubernetes #homelab
=> More informations about this toot | More toots from jokeyrhyme@aus.social
@jokeyrhyme I've never heard of seaweedfs, nice to read up on it. How does it compare to longhorn?
=> More informations about this toot | More toots from everts@mastodon.social
@everts you know, I think I'd been looking for an alternative to longhorn back when I was playing with talos ( https://www.talos.dev/ ) because back then they were incompatible (and might still be)
so, now that I'm not using talos, maybe I ought to try out longhorn, too
as far as I can tell, longhorn and seaweedfs have a similar feature set, and longhorn might even work better with k3s given that it's officially documented there: https://docs.k3s.io/storage#setting-up-longhorn
one thing I liked with seaweedfs is that there's an operator for it, so the entire setup can be running within k8s (I can't tell if longhorn has something similar)
=> More informations about this toot | More toots from jokeyrhyme@aus.social
@jokeyrhyme I'm missing the comparison in their docs, but that could be because its focus is broader than k8s
=> More informations about this toot | More toots from everts@mastodon.social
@everts yeah, I can find articles comparing longhorn to a bunch of older/slower/complicated systems, and articles comparing seaweedfs to a bunch of older/slower/complicated systems, but nothing comparing longhorn to seaweedfs :P
=> More informations about this toot | More toots from jokeyrhyme@aus.social
@jokeyrhyme i was planning on using longhorn, maybe we should colab
=> More informations about this toot | More toots from everts@mastodon.social
@everts well, longhorn works well enough across microSD cards for the I/O workload from pi-hole (well, just starting the process and logging into web console)
Not much harder to setup than k3s itself, which is nice, although operating both is going to be more demanding than just installing (e.g. debugging, disaster recovery, expansion)
I need to solve UDP routing so that I can actually use pi-hole here, but this was enough to get it up and running and storing its files in longhorn: https://gitlab.com/jokeyrhyme/dotfiles/-/merge_requests/45
=> More informations about this toot | More toots from jokeyrhyme@aus.social
@jokeyrhyme seems do-able
=> More informations about this toot | More toots from everts@mastodon.social This content has been proxied by September (ba2dc).Proxy Information
text/gemini