addon-controller VS cluster-api

👏 Support this project Every contribution counts! If you enjoyed this article, check out the Projectsveltos GitHub repo. You can star 🌟 the project if you find it helpful.

Sveltos is an open-source Kubernetes project to deploy add-ons in a multitude of Kubernetes cluster. Sveltos can also be instructed to watch for changes in ConfigMaps and Secrets and triggers rolling upgrades for the associated resources, ensuring that applications stay up-to-date.

If you enjoyed this article, please check out the GitHub repo for the project. You can also star 🌟 the project if you found it helpful. The GitHub repo is a great resource for getting started with the project. It contains the code, documentation, and examples. You can also find the latest news and updates on the project on the GitHub repo. Thank you for reading!

And if you like it, please star ⭐ the project on GitHub

With projectsveltos, you can instruct add-on controller to deploy resources using Kustomize (on top of Helm charts and regular YAMLs). Then you could use its event-driven framework to deploy extra resources on demands.

When deploying add-ons with Sveltos Kuberntes add-on controller it is now possible to also enforce add-on constraints (defined in the management cluster using openapi).

Open a bug/feature enhancement on github

Here for instance https://github.com/projectsveltos/sveltos-manager/blob/main/.github/workflows/main.yaml

Documentation can be found here

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.