Missing 7.17.x charts (chart version not aligned with image tag)?
brsolomon-deloitte opened this issue ยท 6 comments
Is the Elastic team still supporting Elastic stack 7.17.x releases for these Helm charts? It looks like most of the charts were last updated about six months ago to use the 7.17.3
images by default whereas 7.17.6 is the latest patch release.
If there are no plans to update the 7.17
branch here, could that be pinned as a GitHub Issue?
Hey @brsolomon-deloitte,
Indeed, we didn't release versions after 7.17.3, and decided to not release new version of charts for every patch version.
Not sure if we'll release newer 7.17.x versions but you can use the 7.17.3 chart version with new stack images by setting imageTag
value.
Helm best practice is to not override the image version in a helm chart (to ensure compatibility between the deployment and the container image).
Could elastic please reconsider their position on this?
Helm best practice is to not override the image version in a helm chart
Can you add more details and sources?
90% of the Helm charts do have a value to override the image tag. This is also part of the official Helm chart template when using the helm create
command and has been mentioned as a best practice by Helm maintainers in the PR that added it: helm/helm#7878 (comment)
While we ourself recommend using the same version for the Helm chart and the Docker image in the doc, we don't release any more new charts version for all patch releases, so you can override the Docker image tag for a more recent patch version (for example 7.17.3 chart with 7.17.5 images).
Can you add more details and sources? 90% of the Helm charts do have a value to override the image tag.
Yes, but 90% of Helm charts also follow the best practices of:
- Keeping the default image tag at an up-to-date (latest patch release) version
- Properly bumping the chart version whenever the default image tag is bumped
Bitnami charts are one good example.
๐๐ป FYI, following 8.5.1 release, we also published an official communication in #1731 about the future of this repository.