Release tag pulsar-2.9.3 is not matching the images version in values.yaml

[youg9203]

Hello,

Is that intentional or a mistake, I believe it supposes to match the pulsar version, if not then I would suggest adding the build number in the version, the original version must be synced with the apache-pulsar version.

Please correct me if I'm wrong, or did I miss something here?

Thanks

[pgier]

If you look at the app version of the 2.9.3 release of the Helm chart, you can see that it still points to version 2.9.2 of Pulsar. However, I agree with you, that it would be nice if these versions were kept in sync. So in this case it probably would have been better to use a version something like 2.9.2_1 to make it more obvious which version of Pulsar this release uses, especially considering that there will likely be a 2.9.3 release of Pulsar soon.

@sijie @michaeljmarshall WDYT, can we keep future releases of the Helm chart synced to the Pulsar version, and use an optional build/patch number to indicate that something was fixed in the chart?

[michaeljmarshall]

The chart's version does not need to align with the version of Apache Pulsar that ships with it by default. That is the purpose of the appVersion field in the Chart.yaml see here https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/Chart.yaml.

The primary reason we have diverged is that it is helpful to decouple helm chart and Apache Pulsar releases so that helm chart features can ship faster. That being said, we could probably do a better job of documenting the version of pulsar that the chart is currently using. Maybe we could do this with some kind of button at the top of the README?