Harbor
chartmuseum
Our great sponsors
Harbor | chartmuseum | |
---|---|---|
74 | 8 | |
22,318 | 3,470 | |
2.2% | 1.1% | |
9.7 | 0.0 | |
6 days ago | 8 days 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.
Harbor
-
Docker Private Registry using Harbor
cat << EOF wget \ https://github.com/goharbor/harbor/releases/download/v2.9.4/\ harbor-offline-installer-v2.9.4.tgz EOF
-
Signing container images: Comparing Sigstore, Notary, and Docker Content Trust
Now that you know a little more about Cosign, Notary, and DCT, we will take it one step further by using one of these tools: Cosign. For this example, we will use the simple Docker registry:2 reference image to run a simple registry. In a real-world scenario, a managed registry such as Harbor, Amazon ECR, Docker Hub, etc.
- Docker pull through cache to multiple upstreams, that you can also push to
-
tcp i/o timeout when installing network plugin in "high secure environment"
Have a look at harbor, you can also use it to follow the same methods for helm charts etc.
-
How to build a docker image and still use Watchtower
Or for something more advanced https://goharbor.io/
-
Scan selfhosted docker images for vulnerabilities automatically
Look at https://goharbor.io/
-
Docker has reversed its decision to sunset the “Docker Free Team” plan.
You can host your own image repo if your feeling feisty. Harbor is a graduated project from the CNCF and they are also working on a new implementation called Dragonfly. https://goharbor.io/
- We're no longer sunsetting the Free Team plan | Docker
-
Docker's deleting Open Source images and here's what you need to know
Does anybody know whether there could be something like an open/libre container registry?
Maybe the cloud native foundation or the linux foundation could provide something like this to prevent vendor lock-ins?
I was coincidentially trying out harbor again over the last days, and it seems nice as a managed or self-hosted alternative. [1] after some discussions we probably gonna go with that, because we want to prevent another potential lock-in with sonarpoint's nexus.
Does anybody have similar migration plans?
[1] https://goharbor.io
-
Iron Bank: Secure Registries, Secure Containers
2) Harbor instance registry
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.
What are some alternatives?
Portainer - Making Docker and Kubernetes management easy.
helm-diff - A helm plugin that shows a diff explaining what a helm upgrade would change
Dragonfly - This repository has be archived and moved to the new repository https://github.com/dragonflyoss/Dragonfly2.
helm-push - Helm plugin to push chart package to ChartMuseum
phoneinfoga - Information gathering framework for phone numbers
helm - The Kubernetes Package Manager
gitlab
tailscale - The easiest, most secure way to use WireGuard and 2FA.
distribution - The toolkit to pack, ship, store, and deliver container content
hub-feedback - Feedback and bug reports for the Docker Hub
ingress-nginx - Ingress-NGINX Controller for Kubernetes
go-echarts - 🎨 The adorable charts library for Golang