Helm charts can be seen as docker/container images for Kubernetes manifests in terms of their packaging i.e. a Helm chart consists of a .tgz archive with metadata and manifests inside of it.
With this in mind, we should treat our built Helm charts like docker images:
[x] Every built Helm chart uses a hash of the contents as its version (like a tagged docker image).
[ ] Releasing a Helm chart should not involve hard-coding versions. i.e. we could provide tooling/scripts to release Helm charts upon tagged git versions.
Helm charts can be seen as docker/container images for Kubernetes manifests in terms of their packaging i.e. a Helm chart consists of a
.tgzarchive with metadata and manifests inside of it. With this in mind, we should treat our built Helm charts like docker images: