chartmuseum VS helm-diff

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?

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?

You can use either something like https://chartmuseum.com/ or any docker registry if it has OCI support.

ChartMuseum is indeed open source and is on GitHub.

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

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.

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.

#!/usr/bin/env bash set -euo pipefail cd "$(dirname "$0")/.." source scripts/common.sh green "Installing Kubectl" install_kubectl green "Installing helm version => ${HELM_VERSION}" install_helm green "Setting up Kong Helm Repo" helm repo add kong https://charts.konghq.com helm repo update green "Installing Helm Diff Plugin" helm plugin install https://github.com/databus23/helm-diff || true green "Setting up AWS Auth" setup_aws_auth green "Set the current namespace" kubectl config set-context --current --namespace=${KONG_NAME}-kong green "Validating VPA Config => ${KONG_NAME}-kong-vpa" kubectl diff -f ${KONG_NAME}/vpa.yaml || true if [[ "${KONG_NAME}" == prd ]]; then green "Validating Ingress => ${KONG_NAME}-kong-ingress" kubectl diff -f ${KONG_NAME}/ingress.yaml || true fi green "Validating Kong => ${KONG_NAME}" helm diff upgrade \ --install \ "${KONG_NAME}" \ kong/kong \ --namespace "${NAMESPACE}" \ -f ${KONG_NAME}/kong.yaml \ --set-file dblessConfig.config=${KONG_NAME}/declarative.yaml \ --version 2.6.3

helm plugin install https://github.com/databus23/helm-diff helm plugin install https://github.com/aslafy-z/helm-git helm plugin install https://github.com/jkroepke/helm-secrets

helm-diff plugin to see differences about what will be deployed.

There's Helm plugin (https://github.com/databus23/helm-diff) that show diff results for you, for example

    helm diff upgrade   --namespace 

So helm secrets is a helm plugin, not quite native. It requires the helm diff plugin as well.