#helmfile - December 2022

Does anybody validate helmfile’s values somehow? We’ve got a scenario when we want to make folks use only numbers as a value and we want to fail the ci pipeline if this requirement is not met. i.e.

myKey: 12345 # valid

myKey: qwerty # not valid

I know that something like that was added to Helm (https://www.arthurkoziel.com/validate-helm-chart-values-with-json-schemas/), but we are interested in helmfile’s values validation, not Helm’s.

Hey all, is there a way to capture the helmfile deployment REVISION number within and use it within a values.yaml.gotmpl ?

helmfile template takes a long time to run for my project. We have a parent helmfile which includes many sub helmfiles (~20). Many of the helmfiles add the same repos, so we spend a lot of time building deps, i.e.

Building dependency release=releaseA, chart=<my local chart>
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "<some chart repo here>" chart repository

And this is repeated for the exact same deps in each of our 20+ sub helmfiles.

Any advice for reducing the time that helmfile template takes in our parent helmfile?

https://github.com/helmfile/helmfile/releases/tag/v0.149.0 released. enjoy it.🤗

New feature
1. Declare the use of --reuse-values in helmDefaults (#527)
2. Pass helmfile.yaml via stdin using -f - (#520)
3. The secrets field now accept go-getter URLs as well (#560)
4. Declare the use of Helm's --post-render via Helmfile flags, helmfile.yaml helmDefaults and release fields (#510)
5. Support helm v3.10.3 (#579)

hello all. I have a repo with expired cert and I set the

skipTLSVerifly: true

but I still cannot use helmfile apply. Any idea ?