sveltosctl
sveltos-manager
sveltosctl | sveltos-manager | |
---|---|---|
5 | 2 | |
19 | 57 | |
- | - | |
8.2 | 10.0 | |
8 days ago | about 1 year ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sveltosctl
-
5-Step Approach: ProjectSveltos Event Framework for Kubernetes Deployment with Cilium Gateway API
Once the RKE2 cluster is in a “Running” state, we will use the sveltosctl to register it. For the registration, we need three things: a service account, a kubeconfig associated with that account and a namespace. If you are unsure how to create a Service Account and an associated kubeconfig, there is a script publicly available to help you out.
-
5-Step Approach: Projectsveltos for Kubernetes add-on deployment and management on RKE2
The Sveltosctl, is the command-line interface (CLI) for Sveltos. This is an available option to query Sveltos resources and it is available as a Kubernetes pod or as a binary.
-
Collecting tech-supports from managed Kubernetes clusters (and more)
sveltosctl can be used to display collected techsupports.
-
Kubernetes multi-tenancy with projectsveltos
Using sveltosctl we can verify Sveltos is aware system-admin has full access to managed cluster with label env:production
-
Projectsveltos: Manage Kubernetes addons in multiple clusters
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:
sveltos-manager
-
5-Step Approach: Projectsveltos for Kubernetes add-on deployment and management on RKE2
To allow Sveltos to deploy and manage Kubernetes add-ons, the concept of ClusterProfile and cluster labelling comes into play. ClusterProfile is the CustomerResourceDefinition used to instruct Sveltos which add-ons to deploy on a set of clusters.
-
Dynamic Customization of Kubernetes add-ons using Sveltos: Runtime Data Generation
Open a bug/feature enhancement on github contributions welcome Chat with us on the Slack in the #projectsveltos channel Slack
What are some alternatives?
addon-controller - Sveltos Kubernetes add-on controller programmatically deploys add-ons and applications in tens of clusters. Support for ClusterAPI powered clusters, Helm charts, kustomize ,YAMLs. Sveltos has built-in support for multi-tenancy.
argo-cd - Declarative Continuous Deployment for Kubernetes
sveltos - Contains documentation for projectsveltos
demos - Collection of Sveltos demo
gcs-storage-operator - Create Storage Bucket
sveltos-agent - Classify cluster and report back to management cluster. Evaluates cluster health based on custom health checks. Watches for events and reports those to management cluster.