Dapr: Add appVersion to Helm Chart

Created on 13 Mar 2020 · 7Comments · Source: dapr/dapr

In what area(s)?

/area test-and-release

Describe the feature

Currently there's no way to tell what helm chart corresponds to what Dapr version (also it looks like only one helm chart version is listed in the index?).

It be nice if appVersion was listed. Also some of the other optional but nice fields like home & sources, but mostly appVersion

arerelease-eng kinfeature

Source

RichiCoder1

Most helpful comment

@youngbupark global.tag is not enough. If the Chart has changed like extra parameters to the runtime, for example, you will not be able to run older versions just by using the tag.

It's relatively easy for us to add Helm chart versions instead of overriding it every time. What do you think?

yaron2 on 16 Mar 2020

👍2

All 7 comments

This would be helpful for installing older dapr versions

Currently installing dapr through the helm repository will use the latest helm chart (and with this also the latest dapr release)
helm install dapr dapr/dapr --namespace dapr-system

@RichiCoder1: Yes, currently there only seems to be one helm chart version

To install an earlier dapr release (and ensure that the dapr system pods inject the correct dapr version), you have to:

Clone the specific dapr release branch (e.g. 0.4.0 release branch)
Run helm install from /charts/dapr
helm install dapr . --namespace dapr-system --set global.tag=0.4.1

chleit on 15 Mar 2020

Thanks for the suggestion. basically, we control dapr version by global.tag value. But I think using appVersion looks right way better than global.tag. Also dapr helm is likely to have a breaking change until Dapr hits 1.0.0 version. @chleit 's suggestion is the easiest way to use the older version of Dapr now.

youngbupark on 16 Mar 2020

@youngbupark global.tag is not enough. If the Chart has changed like extra parameters to the runtime, for example, you will not be able to run older versions just by using the tag.

It's relatively easy for us to add Helm chart versions instead of overriding it every time. What do you think?

yaron2 on 16 Mar 2020

👍2

@youngbupark global.tag is not enough. If the Chart has changed like extra parameters to the runtime, for example, you will not be able to run older versions just by using the tag.

It's relatively easy for us to add Helm chart versions instead of overriding it every time. What do you think?

Yeah, sounds good. each chart has the version already. @yaron2 is there a way to push to repo with the chart version ?

helm search repo dapr
NAME        CHART VERSION   APP VERSION DESCRIPTION                        
dapr/dapr   0.2.2           1.0         A Helm chart for Dapr on Kubernetes

youngbupark on 16 Mar 2020

@youngbupark global.tag is not enough. If the Chart has changed like extra parameters to the runtime, for example, you will not be able to run older versions just by using the tag.
It's relatively easy for us to add Helm chart versions instead of overriding it every time. What do you think?

Yeah, sounds good. each chart has the version already. @yaron2 is there a way to push to repo with the chart version ?
helm search repo dapr
NAME      CHART VERSION   APP VERSION DESCRIPTION                        
dapr/dapr 0.2.2           1.0         A Helm chart for Dapr on Kubernetes

Yes.

We should get that automated too while we're at it :)

yaron2 on 16 Mar 2020

🚀1

There are now Helm charts for each version of Dapr runtime that is released.