claudie VS demos

Claudie simplifies the process of programmatically establishing Kubernetes clusters across multiple cloud vendors and on-premises datacenters. It provides a centralized management interface for provisioning and managing clusters, eliminating the need for manual configuration and maintenance. Claudie's capabilities include:

I'm one of the authors of https://github.com/berops/claudie

There's also Hetzner bootstrapping information specifically here: https://github.com/berops/claudie/blob/master/docs/input-manifest/providers/hetzner.md

can be found here.

The ConfigMap referenced by EventBasedAddOn instance contains all resources that will be deployed in each cluster where a Pod in crashing state is found. In this case:

All YAMLs used in this example can be found here


https://github.com/projectsveltos/sveltosctl#display-outcome...

But I was still not happy. Main reason, users still had to go and manage cluster labels. I wanted clusters' labels to change as cluster runtime state was changing. So I can express my intent and then forget about it.

So I introduced a second concept in Sveltos. Classifier CRD (https://github.com/projectsveltos/demos/blob/main/classifier...) which allows users to classify clusters based on cluster runtime state (currently kubernetes version and/or resources deployed, but I am working on adding more).

Doing so I can easily now say:

1) I wanted a controller running in the management cluster, so I can express my intent and as clusters come and go or change their runtime state, controller can make sure my intent is applied. For instance, combing Classifier and ClusterProfile I can say things like, in any cluster running kubernetes version v1.24.x install calico v3.23 and in any cluster running kubernetes version v1.25.x install calico v3.24. as clusters are created/upgraded, sveltos makes sure my intent is deployed (https://github.com/projectsveltos/demos/blob/main/classifier/classifier.gif)

So a second concept was introduced in Sveltos: Classifier CRD (https://github.com/projectsveltos/demos/blob/main/classifier/classifier.gif) which allows users to classify clusters based on cluster runtime state (currently Kubernetes version and/or resources deployed, but I am working on adding more).