ansible-role-k3s VS homelab

There is another very good ansible role for k3s, actually better than mine

if you have experience with ansible you can use https://github.com/PyratLabs/ansible-role-k3s

Not OP but there's an excellent galaxy ansible role for k3s and it's idempotent, so if you want to upgrade to a newer version of k3s or tweak settings, or add a node it's supported.

Take it to the next level and let git be the source of truth for k8s using Flux! My home cluster repo is exactly that plus I'm using the ansible-k3s-role Galaxy role. It's based on this k8s at home template.

If you are comfortable with ansible there's a nice Galaxy role that I use.

Experience has been good so far but this is the first I saw of KubeEdge. I’m going to give it an evaluation. I used Ansible https://github.com/PyratLabs/ansible-role-k3s to set up the cluster with some minor adaptions and cleanup scripts.

At home in my Homelab I use PXE to provision bare metal nodes, and Ansible to deploy k8s on them. I know this setup isn't really used for anything yet, but I'm kinda proud of it. I can reprovision nodes at will by simply issuing one command, no monitor needed, no keyboard needed. That's the same level of comfort as a hypervisor, but it's bare metal.

This is my new repo for my homelab and it includes a k8s.yml file, which is much cleaner and uses more Ansible roles to keep various tasks separated. So you can easily break off k8s.yml and all the k8s roles into your own repo if you want to steal it. I'm not completely done with this setup though, I'm testing FluxCD right now because I might want to ditch ArgoCD.

I ended up writing my own, twice actually. Just re-wrote my entire k8s setup for my new homelab. It's published here on gitlab.com. It's not very well documented since it's for personal use but I think it emphasizes how easy it is to setup kubeadm and why there is little reason to make it more complicated than it needs to be.