{"id":22598944,"url":"https://github.com/projectsveltos/helm-charts","last_synced_at":"2026-03-15T20:19:26.932Z","repository":{"id":65729219,"uuid":"598359892","full_name":"projectsveltos/helm-charts","owner":"projectsveltos","description":"Sveltos is tool for managing Kubernetes add-ons in tens of clusters. Support for ClusterAPI powered clusters and helm charts. Sveltos has built-in support for multi-tenancy.","archived":false,"fork":false,"pushed_at":"2026-02-16T07:37:48.000Z","size":1022,"stargazers_count":8,"open_issues_count":7,"forks_count":16,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-02-16T15:40:20.431Z","etag":null,"topics":["add-on","clusterapi","helm","kubernetes","management","multitenancy"],"latest_commit_sha":null,"homepage":"","language":"Go Template","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/projectsveltos.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2023-02-07T00:06:03.000Z","updated_at":"2026-02-16T07:37:37.000Z","dependencies_parsed_at":"2023-10-12T21:17:56.283Z","dependency_job_id":"a41b70b4-4aa2-48fd-8a00-28332a5f110d","html_url":"https://github.com/projectsveltos/helm-charts","commit_stats":null,"previous_names":[],"tags_count":180,"template":false,"template_full_name":null,"purl":"pkg:github/projectsveltos/helm-charts","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/projectsveltos%2Fhelm-charts","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/projectsveltos%2Fhelm-charts/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/projectsveltos%2Fhelm-charts/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/projectsveltos%2Fhelm-charts/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/projectsveltos","download_url":"https://codeload.github.com/projectsveltos/helm-charts/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/projectsveltos%2Fhelm-charts/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29578139,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-18T08:38:15.585Z","status":"ssl_error","status_checked_at":"2026-02-18T08:38:14.917Z","response_time":162,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["add-on","clusterapi","helm","kubernetes","management","multitenancy"],"created_at":"2024-12-08T11:07:33.836Z","updated_at":"2026-02-18T12:01:22.245Z","avatar_url":"https://github.com/projectsveltos.png","language":"Go Template","funding_links":[],"categories":[],"sub_categories":[],"readme":"## Usage\n\n[Helm](https://helm.sh) must be installed to use the charts. Please refer to\nHelm's [documentation](https://helm.sh/docs) to get started.\n\nOnce Helm has been set up correctly, add the repo as follows:\n\n```bash\nhelm repo add projectsveltos https://projectsveltos.github.io/helm-charts\n```\n\nIf you had already added this repo earlier, run `helm repo update` to retrieve\nthe latest versions of the packages. You can then run `helm search repo\nprojectsveltos` to see the charts.\n\nTo install the projectsveltos chart:\n\n```bash\nhelm install projectsveltos projectsveltos/projectsveltos \\\n  --create-namespace -n projectsveltos\n```\n\nBy default the chart will install in agent mode. To install in agentless mode, add the argument: `--set agent.managementCluster=true` to the above command.\n\nAll the available Helm chart values are located at the [values.yaml](./charts/projectsveltos/values.yaml) file.\n\n**Note Upgrade Information**\n\n- **Sveltos v1.1.1 and later**\n    - **Manifest:** Simply apply the latest manifest available. The YAML directly updates CRDs and all components.\n    - **Helm Chart:** The Sveltos Helm chart automatically updates CRDs before other components using a built-in Job.\n- **Sveltos v1.1.0 and earlier**\n    - **Helm Chart:** Follow the standard [Helm chart upgrade process](https://helm.sh/docs/helm/helm_upgrade/).\n    - **Sveltos Helm Chart and CRDs Helm Chart:** If Sveltos was initially deployed using separate Helm charts for Sveltos and its CRDs, this approach must be maintained for all upgrades. Switching to the combined chart installation or upgrade is **not supported**. The Sveltos CRDs Helm chart should be upgraded first, followed by the main Sveltos chart.\n\nTo uninstall the chart:\n\n```bash\nhelm delete projectsveltos -n projectsveltos\n```\n\n# What is the Projectsveltos?\n\nSveltos is a Kubernetes add-on controller that simplifies the deployment and management of add-ons and applications across multiple clusters. It runs in the management cluster and can programmatically deploy and manage add-ons and applications on any cluster in the fleet, including the management cluster itself. Sveltos supports a variety of add-on formats, including Helm charts, raw YAML, Kustomize, Carvel ytt, and Jsonnet.\n\n\u003cp align=\"center\"\u003e\n  \u003cimg alt=\"Sveltos Kubernetes add-ons management across clusters\" src=\"https://projectsveltos.github.io/sveltos/assets/multi-clusters.png\" width=\"600\"/\u003e\n\u003c/p\u003e\n\nSveltos allows you to represent add-ons and applications as templates. Before deploying to managed clusters, Sveltos instantiates these templates. Sveltos can gather the information required to instantiate the templates from either the management cluster or the managed clusters themselves. This enables you to use the same add-on configuration across all of your clusters, while still allowing for some variation, such as different add-on configuration values. In other words, Sveltos lets you define add-ons and applications in a reusable way. You can then deploy these definitions to multiple clusters, with minor adjustments as needed. This can save you a lot of time and effort, especially if you manage a large number of clusters.\n\nSveltos provides precise control over add-on deployment order. Add-ons within a Profile/ClusterProfile are deployed in the exact order they appear, ensuring a predictable and controlled rollout. Furthermore, ClusterProfiles can depend on others, guaranteeing that dependent add-ons only deploy after their dependencies are fully operational. Finally Sveltos' event-driven framework offers additional flexibility. This framework allows for deploying add-ons and applications in response to specific events, enabling dynamic and adaptable deployments based on your needs.\n\n👉 To get updates [⭐️ star](https://github.com/projectsveltos/addon-controller/stargazers) this repository.\n\n## Profiles vs. ClusterProfiles\n\nProjectsveltos offers two powerful tools for managing cluster configurations: **Profiles** and **ClusterProfiles**. Understanding their distinctions is crucial for efficient setup and administration.\n\n1. ClusterProfiles: Apply across all clusters in any namespace. Ideal for platform admins maintaining global consistency and managing settings like networking, security, and resource allocation.\n2. Profiles: Limited to a specific namespace, granting granular control to tenant admins. This isolation ensures teams manage, from the management cluster, their managed clusters independently without impacting others.\n\n\u003cp align=\"center\"\u003e\n  \u003cimg alt=\"Sveltos Profile vs ClusterProfile\" src=\"https://projectsveltos.github.io/sveltos/assets/profile_vs_clusterprofile.png\" width=\"600\"/\u003e\n\u003c/p\u003e\n\n## Addon deployment: how it works\n\nThe idea is simple:\n\n1. from the management cluster, selects one or more `clusters` with a Kubernetes [label selector](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors);\n2. lists which `addons` need to be deployed on such clusters.\n\nwhere term:\n\n1. `clusters` represents both [CAPI cluster](https://github.com/kubernetes-sigs/cluster-api/blob/main/api/v1beta1/cluster_types.go) or any other Kubernetes cluster registered with Sveltos;\n2. `addons` represents either an [helm release](https://helm.sh), Kubernetes resource YAMLs or [kustomize](https://github.com/kubernetes-sigs/kustomize) resources.\n\nHere is an example of how to require that any CAPI Cluster with label _env: prod_ has following features deployed:\n\n1. Kyverno helm chart (version v3.0.1)\n2. kubernetes resource(s) contained in the referenced Secret: _default/storage-class_\n3. kubernetes resource(s) contained in the referenced ConfigMap: _default/contour_.\n\n```yaml\napiVersion: config.projectsveltos.io/v1alpha1\nkind: ClusterProfile\nmetadata:\n  name: deploy-kyverno\nspec:\n  clusterSelector: env=prod\n  syncMode: Continuous\n  helmCharts:\n    - repositoryURL: https://kyverno.github.io/kyverno/\n      repositoryName: kyverno\n      chartName: kyverno/kyverno\n      chartVersion: v3.0.1\n      releaseName: kyverno-latest\n      releaseNamespace: kyverno\n      helmChartAction: Install\n      values: |\n        admissionController:\n          replicas: 3\n  policyRefs:\n    - name: storage-class\n      namespace: default\n      kind: Secret\n    - name: contour-gateway\n      namespace: default\n      kind: ConfigMap\n```\n\nAs soon as a cluster is a match for above ClusterProfile instance, all referenced features are automatically deployed in such cluster.\n\n![Kubernetes add-on deployment](https://github.com/projectsveltos/sveltos/blob/main/docs/assets/addons_deployment.gif)\n\nHere is an example using Kustomize:\n\n```yaml\napiVersion: config.projectsveltos.io/v1alpha1\nkind: ClusterProfile\nmetadata:\n  name: flux-system\nspec:\n  clusterSelector: env=fv\n  syncMode: Continuous\n  kustomizationRefs:\n    - namespace: flux-system\n      name: flux-system\n      kind: GitRepository\n      path: ./helloWorld/\n      targetNamespace: eng\n```\n\nwhere GitRepository synced with Flux contains following resources:\n\n```bash\n├── deployment.yaml\n├── kustomization.yaml\n└── service.yaml\n└── configmap.yaml\n```\n\nRefer to [examples](./examples/) for more complex examples.\n\n## Different SyncMode\n\n- _OneTime_: This mode is designed for bootstrapping critical components during the initial cluster setup. Think of it as a one-shot configuration injection:\n  1. Deploying essential infrastructure components like CNI plugins, cloud controllers, or the workload cluster's package manager itself;\n  2. Simplifies initial cluster setup;\n  3. Hands over management to the workload cluster's own tools, promoting modularity and potentially simplifying ongoing maintenance.\n- _Continuous_: This mode continuously monitors ClusterProfiles or Profiles for changes and automatically applies them to matching clusters. It ensures ongoing consistency between your desired configuration and the actual cluster state:\n  1. Centralized control over deployments across multiple clusters for consistency and compliance;\n  2. Simplifies management of configurations across multiple clusters.\n- _ContinuousWithDriftDetection_: Detects and automatically corrects configuration drifts in managed clusters, ensuring they remain aligned with the desired state defined in the management cluster.\n\n## Configuration Drift Detection\n\nSveltos can automatically detect drift between the desired state, defined in the management cluster, and actual state of your clusters and recover from it.\n\n\u003cp align=\"center\"\u003e\n  \u003cimg alt=\"Configuration drift recovery\" src=\"https://github.com/projectsveltos/demos/blob/main/configuration_drift/reconcile_configuration_drift.gif\" width=\"600\"/\u003e\n\u003c/p\u003e\n\n[![Projectsveltos intro](https://img.youtube.com/vi/FRYYHAWr0MQ/0.jpg)](https://www.youtube.com/watch?v=FRYYHAWr0MQ)\n[![Projectsveltos intro](https://img.youtube.com/vi/A5Y0XTnoS7k/0.jpg)](https://www.youtube.com/watch?v=A5Y0XTnoS7k)\n\n## Give projectsveltos a try\n\nIf you want to try projectsveltos with a test cluster:\n\n1. git clone https://github.com/projectsveltos/addon-controller\n2. make quickstart\n\nwill create a management cluster using Kind, deploy clusterAPI and projectsveltos, create a workload cluster powered by clusterAPI.\n\n## Contributing\n\n❤️ Your contributions are always welcome! If you want to contribute, have questions, noticed any bug or want to get the latest project news, you can connect with us in the following ways:\n\n1. Open a bug/feature enhancement on github [![contributions welcome](https://img.shields.io/badge/contributions-welcome-brightgreen.svg?style=flat)](https://github.com/projectsveltos/sveltos-manager/issues)\n2. Chat with us on the Slack in the #projectsveltos channel [![Slack](https://img.shields.io/badge/join%20slack-%23projectsveltos-brighteen)](https://join.slack.com/t/projectsveltos/shared_invite/zt-1hraownbr-W8NTs6LTimxLPB8Erj8Q6Q)\n3. [Contact Us](mailto:support@projectsveltos.io)\n\n## License\n\nCopyright 2022.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n    http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fprojectsveltos%2Fhelm-charts","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fprojectsveltos%2Fhelm-charts","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fprojectsveltos%2Fhelm-charts/lists"}