▶ helm version --tls
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
~
▶ helm repo list
NAME URL
stable https://kubernetes-charts.storage.googleapis.com
incubator https://storage.googleapis.com/kubernetes-charts-incubator
stakater https://stakater.github.io/stakater-charts
flagger https://flagger.app
bitnami https://charts.bitnami.com/bitnami
~
▶ helm repo update --debug
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "flagger" chart repository
...Successfully got an update from the "stakater" chart repository
...Successfully got an update from the "incubator" chart repository
...Successfully got an update from the "bitnami" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
~
▶ helm search repo bitnami/postgresql
No results found
~
▶ helm search repo bitnami/mariadb -l
No results found
However this works (have to escape ~ on zsh)
▶ helm search postgresql --version \~8.9.0
NAME CHART VERSION APP VERSION DESCRIPTION
bitnami/postgresql 8.9.9 11.8.0 Chart for PostgreSQL, an object-relational data...
How can I specify a repo to search in?
It looks like the Helm repo search functionality only available since v3.0.0.
Even I tried using the latest v2.16.7 version, still no luck.
$ helm version
Client: &version.Version{SemVer:"v2.16.7", GitCommit:"5f2584fd3d35552c4af26036f0c464191287986b", GitTreeState:"clean"}"
$ helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" has been added to your repositories
$ helm repo update --debug
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "stable" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete.
$ helm repo list
NAME URL
stable https://kubernetes-charts.storage.googleapis.com
local http://127.0.0.1:8879/charts
bitnami https://charts.bitnami.com/bitnami
$ helm search repo bitnami/postgresql
No results found
But it works well with version 3.0.0 or above.
$ helm version
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}
$ helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" has been added to your repositories
$ helm repo update --debug
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈ Happy Helming!⎈
$ helm repo list
NAME URL
bitnami https://charts.bitnami.com/bitnami
$ helm search repo bitnami/postgresql
NAME CHART VERSION APP VERSION DESCRIPTION
bitnami/postgresql 8.10.2 11.8.0 Chart for PostgreSQL, an object-relational data...
bitnami/postgresql-ha 3.2.7 11.8.0 Chart for PostgreSQL with HA architecture (usin...
Related
This is my chart:
name: zookeeper
version: 1.0.0
dependencies:
- name: bitnami/zookeeper
version: 3.8.1
repository: https://charts.bitnami.com/bitnami
This is what my helm search repo zookeeper produces:
NAME CHART VERSION APP VERSION DESCRIPTION
bitnami/zookeeper 11.1.2 3.8.1 Apache ZooKeeper provides a reliable, centraliz...
my-repo/zookeeper 11.1.2 3.8.1 Apache ZooKeeper provides a reliable, centraliz...
But when I try to fetch my dependencies, it says the chart doesn't exist:
$ helm dependency build [11:50:45]
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "my-repo" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
Error: bitnami/zookeeper chart not found in repo https://charts.bitnami.com/bitnami
Why? It's there, so why won't it fetch it?
thanks
I had to change the name from bitnami/zookeeper to zookeeper in my chart since that's how it's defined in the base chart
If I perform the following command it looks in "https://github.com/grafana/" instead of the one I specified - "https://grafana.github.io/helm-charts"
Here is what I run and the results:
helm3 upgrade --install grafana grafana --dry-run --repo https://grafana.github.io/helm-charts --wait
Release "grafana" does not exist. Installing it now.
Error: failed to download "https://github.com/grafana/helm-charts/releases/download/grafana-6.16.14/grafana-6.16.14.tgz"
Why is it looking in "github.com/grafana" instead of where I told it to look with the repo flag - "grafana.github.io"?
My co worker runs the same command and it works.
I list the repositories and grafana is not there so I would assume that would force this to work?
helm3 repo list
NAME URL
stable https://charts.helm.sh/stable
local http://127.0.0.1:8879/charts
eks https://aws.github.io/eks-charts
bitnami https://charts.bitnami.com/bitnami
cluster-autoscaler https://kubernetes.github.io/autoscaler
kube-dns-autoscaler https://kubernetes-sigs.github.io/cluster-proportional-autoscaler
cluster-proportional-autoscaler https://kubernetes-sigs.github.io/cluster-proportional-autoscaler
external-dns https://charts.bitnami.com/bitnami
kube2iam https://jtblin.github.io/kube2iam/
kubernetes-dashboard https://kubernetes.github.io/dashboard/
incubator https://charts.helm.sh/incubator
My coworker has the same repo list output as above.
The below commands will work in my system however I want to know why for me it will not work when I use the --repo flag as in the above example (all of our code has that flag in it and they do not want to change it) :
helm3 repo add grafana https://grafana.github.io/helm-charts
"grafana" has been added to your repositories
kconfig_et helm3 upgrade --install grafana grafana/grafana --dry-run --wait
I executed your Helm command but with --debug flag to get this error:
helm upgrade --install grafana grafana --dry-run --repo https://grafana.github.io/helm-charts --wait --debug
history.go:56: [debug] getting history for release grafana
Release "grafana" does not exist. Installing it now.
install.go:178: [debug] Original chart version: ""
Error: no cached repo found. (try 'helm repo update')
Then I simply executed helm repo update as suggested. I then retried the same helm upgrade command and it successfully installed the chart.
You coworker did not encounter the error because at some point he/she has executed helm repo update at least once. (Mine was a freshly installed Helm)
I solved it - I added "--debug" to the command and saw this -
Error: no cached repo found. (try 'helm repo update'): open /Users/mysystem/Library/Caches/helm/repository/local-index.yaml: no such file or directory
I next copied the one in .helm over to the location in the debug message -
cp ~/.helm/repository/local/index.yaml /Users/mysystem/Library/Caches/helm/repository/local-index.yaml
All worked after this!
I am trying to install memcached from helm charts stable repo
My requirements.yaml file looks like this
- name: stable/memcached
repository: https://charts.helm.sh/stable
version: 2.7.1
I am getting this error:
Error: stable/rabbitmq chart not found in repo https://charts.helm.sh/stable
I tried this on my computer
helm repo add stable https://charts.helm.sh/stable
helm search memcached --versions | grep 2.7.1
and I can see
stable/memcached 2.7.1 1.5.12 Free & open source, high-performance, distributed memory ...
Can someone advice why I am seeing this error?
I have just replaced the chart name in my requirements.yaml file
- name: memcached
repository: https://charts.helm.sh/stable
version: 2.7.1
I am trying to download/install the jupyterhub helm chart.
> helm repo add jupyterhub https://jupyterhub.github.io/helm-chart/
"jupyterhub" has been added to your repositories
> helm repo update
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "jupyterhub" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
> helm upgrade --install jhub jupyterhub/jupyterhub --namespace jhub --version=0.8.2 --values config.yaml
Error: failed to download "jupyterhub/jupyterhub" (hint: running `helm repo update` may help)
(trying helm repo update again does not work)
When I look at my repos, I can see jupyterhub:
> helm repo list
NAME URL
stable https://kubernetes-charts.storage.googleapis.com
local http://127.0.0.1:8879/charts
jupyterhub https://jupyterhub.github.io/helm-chart/
what am i missing? could it be upstream repo server issue?
Wow. The problem was that I had quotes around the version. it did not accept that. This works:
helm upgrade --install jhub jupyterhub/jupyterhub --namespace jhub --version=0.8.2 --values config.yaml
Delete the cached archive to force a redownload:
rm -rf ~/.helm/cache/archive/cp-helm-charts-0.1.0.tgz
Do an explicit repo update
helm repo update
Do a debug/dry-run install to force a download:
helm install --debug --dry-run confluent/cp-helm-charts > /dev/null
Look at the specific file in the .tgz archive where I want to see the fix:
tar xfO ~/.helm/cache/archive/cp-helm-charts-0.1.0.tgz cp-helm-charts/charts/cp-kafka/templates/statefulset.yaml | grep -n -C10 volumes:
Compare to the latest version on github, which was modified 8 days ago:
https://github.com/confluentinc/cp-helm-charts/blob/master/charts/cp-kafka/templates/statefulset.yaml#L140
The github version has - name: datadir-0. The version Helm pulls just has - name: datadir without the trailing -0.
Why does the .tgz file that Helm pulls not have the latest fix in the master branch version on github? How do I fix this?
FYI, my relevant environment information:
helm version
Client: &version.Version{SemVer:"v2.12.2", GitCommit:"7d2b0c73d734f6586ed222a567c5d103fed435be", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.12.2", GitCommit:"7d2b0c73d734f6586ed222a567c5d103fed435be", GitTreeState:"clean"}
helm repo list
NAME URL
stable https://kubernetes-charts.storage.googleapis.com
local http://127.0.0.1:8879/charts
confluent https://confluentinc.github.io/cp-helm-charts/
The chart maintainer is distributing a .tgz chart that is not up to date with recent git commits. They recommend you build your own chart .tgz.