Hey Brian, versioning helm chart is not new at all, it's quite essential- it's a general practice followed even in all public chart repos. A chart version, for instance, would change when you modify critical things like, say your configmap template- which essentially changes behaviour of the app. In traditional gitflow, your application release comes from a release branch of your source code. That version alone doesn't determine its complete behavior. Your chart, for instance, supplies configmap that significantly modifies the behavior of your app. You could have the same docker tag of the app 1.1.2 in two different environments with different configs, let's say one with thread_count parameter of 20, and in another environment with thread_count of 40. Those two release version are not the same and should be distinguishable in your CICD pipelines.