system-upgrade-controller VS ansible-role-k3s

Rancher can do this with https://github.com/rancher/system-upgrade-controller

In theory I should use https://github.com/rancher/system-upgrade-controller, but because my homelab is still in active development and I keep nuking it, I never had a chance to upgrade lol

I'm currently bumping the versions manually, but I plan to automate that with system upgrade controller [1] and Dependabot [2] (or similar)

[1]: https://github.com/rancher/system-upgrade-controller

[2]: https://github.com/dependabot

Updating k3s is much easier using their system upgrade controller. I've been using it for a year and no hiccups. Runs in cluster, updates automatically depending on what release channel you want to use.

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.