I would agree with you if talking about reusable Chart for different applications but this Chart is made only for Vault.
Appart from the image tag value that can be setted in a values file, there’s the appVersion value that reside in the Chart.yaml. This oblige to repackage the Chart to set it if we want a clear helm history.
That’s what I’ve done but I would have prefer to keep the official Chart imutable.
You are making unnecessary work for yourself. Just accept that appVersion tells you the version of Vault that that chart version has as a default suggestion, and does not need to be updated when using the chart to deploy a different version.
Even Helm’s own docs point in this direction:
For example, the drupal chart may have an appVersion: "8.2.1" , indicating that the version of Drupal included in the chart (by default) is 8.2.1 .
Sorry for any confusion here, we don’t always release a helm chart update with every new patch release of vault, although it would certainly be expected for a major version change.
As @maxb pointed out, general best practices for production systems are that you should specifically pin (manually set, in your config.yaml overrides file) your application versions.