ansible-role-k3s VS cluster-api

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.

In this blog post, we will demonstrate how easy and fast it is to deploy Sveltos on an RKE2 cluster with the help of ArgoCD, register two RKE2 Cluster API (CAPI) clusters and create a ClusterProfile to deploy Prometheus and Grafana Helm charts down the managed CAPI clusters.

4. Having moved to a container orchestrator, all of my nodes are immutable. Hardware and VM instances _can_ be born magically into existence. Nearly all infra providers support [cluster-api](https://cluster-api.sigs.k8s.io/). Network infrastructure can now be managed with TF, so I go that route.

## Linux curl -L https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.4.4/clusterctl-linux-amd64 -o clusterctl sudo install -o root -g root -m 0755 clusterctl /usr/local/bin/clusterctl ## Mac brew install clusterctl

Did you ever try CAPI? https://github.com/kubernetes-sigs/cluster-api

You might find interesting the capi-rancher-import k8s operator we use in Sylva, it would adopt in Rancher server the Cluster API created k8s clusters (with bootstrap provider kubeadm or even rke2 - you can lookup CAPBR for the latter). I understand your clusters are not created by Cluster API, so if you could move the workloads/resources to new clusters created by Cluster API, this can come handy. (Adoption of non-CAPI clusters into CAPI is not yet a standard practice, more in https://github.com/kubernetes-sigs/cluster-api/issues/7776)

Most of the comments have mentioned older tools like kubespray, Ansible, Rancher etc. I would suggest the cloud native way using ClusterAPI or use a tool that relies on ClusterAPI in the backend called Talos

Cluster API

Sveltos is a powerful open source project that makes managing Kubernetes add-ons a breeze. It automatically discovers ClusterAPI powered clusters and allows you to easily register any other cluster (like GKE). Then, it seamlessly manages Kubernetes add-ons across all your clusters.