Strimzi-kafka-operator: [Bug] Helm3 cli pulls v2 helm chart version in 0.19.0

Created on 28 Jul 2020 · 10Comments · Source: strimzi/strimzi-kafka-operator

Strimzi helm repo contains two versions of helm chart release for 0.19.0, one for helm 2 and other for helm 3.
However, there is no way to get helm v3 client working with v3 chart .

This cause errors in installing/updating operator using helm3 clients when CRDs are previously installed

To Reproduce

$ helm version
version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"clean", GoVersion:"go1.13.12"}

$ helm repo add strimzi https://strimzi.io/charts/ 
"strimzi" has been added to your repositories

$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "strimzi" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈ 

$ helm install --debug  --dry-run test  strimzi/strimzi-kafka-operator
install.go:159: [debug] Original chart version: ""
install.go:176: [debug] CHART PATH: xxx.cache/helm/repository/strimzi-kafka-operator-helm-2-chart-0.19.0.tgz

Error: rendered manifests contain a resource that already exists...

Expected behavior

$ helm install --debug  --dry-run test  strimzi/strimzi-kafka-operator
install.go:159: [debug] Original chart version: ""
install.go:176: [debug] CHART PATH: xxx.cache/helm/repository/strimzi-kafka-operator-helm-3-chart-0.19.0.tgz

and no errors

bug

Source

stoiev

👍1

Most helpful comment

@klalafaryan As we are slowly deprecating Helm v2 (which is being deprecated anyway), I will not add it to the index file anymore in 0.20.0 release (zip file will be still there for download) and I expect it to be removed after the release.

scholzj on 15 Oct 2020

👍3

All 10 comments

Helm 3 generates the index this way. So I'm not sure why is it picking the helm 2 chart from the index later.

scholzj on 28 Jul 2020

Helm 3 generates the index this way. So I'm not sure why is it picking the helm 2 chart from the index later.

I could not find an issue/doc on Helm that states about it, but I found some ways to turn packages multi-version.

There was an initiative from main helm chart repository (stable/*) to achieve this. It seems that _globbing_ CRDs from helm3 crds/ directory for helm2 while maintaining "helm.sh/hook": crd-install annotation do the work.

Just like was done in Prometheus chart, for example.

stoiev on 28 Jul 2020

I don't think we are aspiring to have a chart working for both. We have two charts intentionally. The Helm 2 chart is expected to be deprecated soon.

scholzj on 28 Jul 2020

@sgkiokas Any idea how should we deal with the index? Should we have two separate repositories one for Helm 2 and one for Helm 3?

scholzj on 28 Jul 2020

@scholzj, apologies about the late reply. I don't know from the top of my head I'm afraid. I'll try to do some experimentation and googling to see what we can do for that matter.

sgkiokas on 30 Jul 2020

@sgkiokas We are having the same problem. We have deployed strimzi (0.18.0) using helm 2, and now we would like to bump up strimzi to 0.19.0 using helm 3 but seems like it is not possible.
Any update on this?
Many thanks!