Here you are: Vagrant-Setup with Ansible deploying k3s and GitLab inside k3s.
https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
https://github.com/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
Currently without the Runner, that comes next.
I stumbled into that cool project and it really deserves to get more light! 
Someone's figured out how to turn old smartphones into Kubernetes nodes using postmarketOS and #K3s. Like, whoa!
The idea is to forget about Raspberry Pis and using old phones instead. More power, more RAM, and built-in batteries? Yes, please! 
If you're into Linux and K3s like me, you've GOT to check this out: https://blog.denv.it/posts/pmos-k3s-cluster/
It's got all the details on getting K3s running on postmarketOS.
Self-Hosting a Cluster on Old Phones https://hackaday.com/2025/04/09/self-hosting-a-cluster-on-old-phones/ #handheldshacks #postmarketos #raspberrypi #bootloader #kubernetes #smartphone #unlockable #linux #k3s
Self-Hosting a Cluster on Old Phones - The phones most of us carry around in our pockets every day hold a surprising amou... - https://hackaday.com/2025/04/09/self-hosting-a-cluster-on-old-phones/ #handheldshacks #postmarketos #raspberrypi #bootloader #kubernetes #smartphone #unlockable #linux #k3s
Hello #Community!
Today marks the first(of many) #K3s #Community meetings and Office hours.
We will do twice a month to be able to accommodate AMS/EMEA and EMEA/APAC.
Join us to discuss the future of #k3s how you can get involved and help!
Full information here:
iCal: https://webcal.prod.itx.linuxfoundation.org/lfx/a092M00001IkYIjQAN
A Comparative Analysis of K3s, MicroK8s, and Alternatives
@tailscale I've been using this with #k3s on my #homelab for a while and it's super cool, worth checking out.
Very easy to take a kube service and expose as `https` on your tailnet
Finally got my #Kickstarter-backed #ComputeBlade! Replacing my last #RasperryPi 4 node in the #K3S cluster—now all worker nodes are PoE-powered.
RE: "Impromptu disaster recovery"
Amos talks about how they accidentally nuked their Kubernetes based infra with one happy little accident. As per usual, an informative and fun read!
https://kevingimbel.de/link-blog/re-https-fasterthanli-me-articles-impromptu-disaster-recovery
k3s appears to have had a major upgrade in the last few days. In v1.32.2 they have finally bumped containerd to v2 and traefik to v3
it's not shipped as a default yet, but i have played with it yesterday afternoon, and it all seem to work just fine. well at least for my use cases that is
K3s es una versión ligera y simplificada de Kubernetes, diseñada para ser fácil de instalar y gestionar en entornos de producción pequeños y medianos.
Además del LPP, K3s también admite otros proveedores de PV, como:
Longhorn: Un proveedor de PV que utiliza un sistema de archivos distribuido para almacenar los datos de los volúmenes persistentes.
Bon, je vais devoir reporter le stream d'expérimentation/comparatif #k3s/#talos à la semaine prochaine pour cause de visite familiale (évidemment, maintenant que j'ai un nouvel appart'...). Espérons que les Pi meurent pas entre temps 
What I did in the last weeks (part 2):
All of my k3s clusters (and I have a few of them for $REASONS) are now running either #fluxCD or #argoCD. So everything #gitops now.
In general, I like the lightweightness of fluxCD, not having to run Redis and whatnot. But having a GUI is sometimes nice, even though the flux CLI is really easy to use and very intuitive.
And of course, #renovatebot is watching all repositories and sending merge requests to update things in the clusters. Nice!
Well... After all the nice things I say about #k3s, my cluster decided to eat itself last night lol
No worry though, all I had to do was restore the Longhorn volumes, Ingress, and Cert manager, then hit "go" on my GitLab pipelines :)
A #k3s #homelab is the way to go if you want stability, upgrade-ability, ect., especially with #longhorn and #gitlab
I wrote a blog post on this setup as well: https://blog.mudhut.xyz/new-mini-pc-k3s-cluster/
I may do another on specifically GitLab. I have used it for years at work and it has been fantastic.
Updating Mastodon is literally just me changing "4.3.3" in my #gitlab variables to "4.3.4"... this flow cannot be any more simple.
I also updated the minor version of Ruby, same deal, just a variable
GitLab for a #k3s #homelab is the way to go! You get CI/CD, Container Registry, Helm/Package Registry, and a source control system, all in one... all local...
Ok, #Longhorn might have just saved me here with #k3s and my storage woes. #SMB and #NFS both caused catastrophic problems with corrupted files and databases. Using #unraid as the storage backend for the later 2 but will keep it as a backup destination and network storage for more static datasets.
Thanks to everyone who helped push me in this direction. #homeassistant is officially happy again!
Ok, think I need to do the whole #k3s shared storage thing again. As of last night I have both NFS and SMB going, but neither work for #sqlite DBs of course. I get corruptions on NFS and immediate errors on SMB (can’t get exclusive locks). Thinking of trying #longhorn for the shared storage with off-cluster backup.
My primary use case is apps like #homeassistant though, so I’m not sure if I’m overthinking this. I suppose I could configure HA to use a DB like Maria but I have some apps that don’t support this at all to my knowledge, so I’d need something with proper file locking support.
Has anyone gone down this road? Am
I framing this right - Longhorn for most app storage needs, SMB/NFS for larger storages like photos / media?
