chartmuseum
private-provider-registry-action
Our great sponsors
- SonarLint - Clean code begins in your IDE with SonarLint
- InfluxDB - Access the most powerful time series database as a service
- CodiumAI - TestGPT | Generating meaningful tests for busy devs
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
| chartmuseum | private-provider-registry-action | |
|---|---|---|
| 8 | 2 | |
| 3,210 | 6 | |
| 2.1% | - | |
| 6.0 | 3.5 | |
| 6 days ago | over 2 years ago | |
| Go | Python | |
| 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
-
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?
-
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
-
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.
private-provider-registry-action
-
Self Hosted Module Registry
or https://github.com/jbrunetext/private-provider-registry-action/
What are some alternatives?
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
helm-push - Helm plugin to push chart package to ChartMuseum
helm-diff - A helm plugin that shows a diff explaining what a helm upgrade would change
helm - The Kubernetes Package Manager
tailscale - The easiest, most secure way to use WireGuard and 2FA.
chart-releaser - Hosting Helm Charts via GitHub Pages and Releases
hub-feedback - Feedback and bug reports for the Docker Hub
go-echarts - 🎨 The adorable charts library for Golang
robusta - Kubernetes observability and automation, with an awesome Prometheus integration
k8s-platform-lcm - A faster and easier way to manage the lifecycle of applications and tools, running and living around your Kubernetes platform
debug-toolkit - A modern code-injection framework for Python. Like Pyrasite but Kubernetes-aware.