chartmuseum
helm-push
| chartmuseum | helm-push | |
|---|---|---|
| 8 | 1 | |
| 3,613 | 677 | |
| 0.6% | 0.4% | |
| 6.0 | 1.1 | |
| 3 months ago | 4 months 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.
chartmuseum
- GitHub - helm/chartmuseum: Host your own Helm Chart Repository
-
Do you mirror external helm chart repositories for local use?
We may switch over to Chartmusuem, and something like Charts-Syncer to try to help with this, or maybe abandon the whole idea of mirroring external repositories and just keep our repository hosting internal projects. What are your thoughts on this?
-
Ask r/kubernetes: What are you working on this week?
Also trying to find a small self-hosted container registry (not some beast like goharbor.io) and possibly a Helm chart repository (looking into chartmuseum.com). Anyone got some recommendations?
-
Where do you store your helm charts?
You can use either something like https://chartmuseum.com/ or any docker registry if it has OCI support.
-
Share how you do your CI/CD to Kubernetes
ChartMuseum is indeed open source and is on GitHub.
-
Self Hosted Module Registry
This is also basically an s3 proxy, but it specifically implements the Terraform Registry API so that things like version constraints are handled correctly. If you use Helm at all, an analogous project for charts would be https://github.com/helm/chartmuseum
-
Metadata for chartmuseum
I raised a PR (WIP) https://github.com/helm/chartmuseum/pull/464 but wondering if others would think this is useful or if I just have a niche usecase.
-
Ditching Docker Compose for Kubernetes
Another benefit of Helm is in it's package management. If your application requires another team's application up and running, they can publish their Helm chart to a remote repository like a ChartMuseum. You can then install their application into your Kubernetes by naming that remote chart combined with a local values file. E.g., helm install other-teams-app https://charts.mycompany.com/other-teams-app-1.2.3.tgz -f values-other-teams-app.yaml. This is convenient because it means you don't have to checkout their project and dig through it for their helm charts to get up and running - all you need to supply is your own values file.
helm-push
-
Can you recommend tooling for publishing helm charts?
Where I work, we combine that with the helm-push plugin as part of our CI workflow.
What are some alternatives?
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
helm-s3 - ⎈ Helm plugin that adds support for AWS S3 as a chart repository.
helm-diff - A helm plugin that shows a diff explaining what a helm upgrade would change
helm-mapkubeapis - This is a Helm plugin which map deprecated or removed Kubernetes APIs in a release to supported APIs
hub-feedback - Feedback and bug reports for the Docker Hub
chart-releaser - Hosting Helm Charts via GitHub Pages and Releases
helm - The Kubernetes Package Manager
helm-gcs - Manage Helm 3 repositories on Google Cloud Storage 🔐 **privately**
robusta - Better Prometheus alerts for Kubernetes - smart grouping, AI enrichment, and automatic remediation
charts - ⚠️(OBSOLETE) Curated applications for Kubernetes
chartmuseum - Host your own Helm Chart Repository [Moved to: https://github.com/helm/chartmuseum]