charts VS chartmuseum

I am attempting to install postgres via helm using the latest stable and it isn't installing the persistent volume properly. I am installing it in Minikube and for some reason it doesn't appear to be able to hostMount properly.

I'm trying to run the Jenkins Helm chart. As part of this setup, I'd like to pass in a persistent volume that I provisioned ahead of time (or perhaps exported from another cluster during a migration).

$ kubectl versionClient Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:21:50Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} Looking at the Sonarqube helm chart

I have installed Prometheus on my Kubernetes cluster (hosted on Google Container Engineer) using the Helm chart for Prometheus.

template "mychart.postgresql.fullname" not defined I've seen examples of Charts doing similar things, like the odoo chart. But in here that logic how the postgresql host name is created is copied and an own define in the template is created.

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.