-
Notifications
You must be signed in to change notification settings - Fork 879
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please release a new version of helm chart with the current vault versions #991
Comments
Thanks for opening this! The next vault-helm release will definitely have the latest version as the default image. In the meantime, since the chart isn't tightly coupled to vault features, you're free to set the image version yourself in the values overrides. And it's recommended to set the version explicitly, instead of relying on the chart's default, for anything other than dev mode (just so there are no unexpected upgrades). |
Thank you.
Yes, we are doing this already when the new chart it's not released yet. We are pinning the chart version which in turns pins the image tag, effectively also pinning the vault version as well. It's not a big deal but it is somehow inconvenient as there are at least 3 places that need to be changed in order to have the same vault image tag. An alternative could be to use |
I would also appreciate to receive vault updates via the helm chart releases, since it's a guarantee that the helmchart is compatible with vault version used. |
I would also prefer to receive helm chart releases matching the vault releases, as that would give "renovate" a chance to catch that there is a new version of the helm chart available. Maybe setup something like "dependabot" to auto-update this chart when it sees a new release of vault? We would also like to not have to track which versions of helm chart are compatible with which versions of vault and vault-k8s, unless we are in a very unique configuration, we prefer to use the version of the application indicated by the helm chart. Thanks, |
Current release is v1.15.4 and it contains security updates
The text was updated successfully, but these errors were encountered: