You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a setup which involves several charts from the stable repo as well as self hosted repos. We would like to periodically update the charts in a convenient manner.
Proposed Solution:
New flag --force-latest for apply and diff commands which would apply/diff the charts with the latest version (should ideally not be run with --skip-repo-update)
New subcommand freeze. Would populate the version number in helmfile.yaml/helmfile.d with what is installed in the cluster. Similar to a pip freeze functionality of python.
The text was updated successfully, but these errors were encountered:
Notes: --force-latest could better be named --dev or --force-dev-versions to be consistent with helm's --dev flag.
Regarding 2, I've proposed helmfile.lock.yaml generated as part of helm dependency update in #483. Perhaps it can be updated via a command similar to pip freeze - helmfile update, helmfile freeze, etc?
New flag --force-latest for apply and diff commands which would apply/diff the charts with the latest version (should ideally not be run with --skip-repo-update)
You should add version constraint to each release in the helmfile state file, like version: > 1.5.0 if you want to avoid getting latest chart versions on helmfile deps.
Background
We have a setup which involves several charts from the stable repo as well as self hosted repos. We would like to periodically update the charts in a convenient manner.
Proposed Solution:
pip freeze
functionality of python.The text was updated successfully, but these errors were encountered: