#helmfile (2024-02)
Questions and discussion around helmfile https://github.com/roboll/helmfile and https://github.com/cloudposse/helmfiles
Archive: https://archive.sweetops.com/helmfile/
2024-02-01
2024-02-07
Is there a way to prevent deletion of charts downloaded by helmfile? I can see options to preserve the values files but not the charts themselves
We store them on our own repo and when we use a 3rdparty, then we cache it in our own env.
2024-02-15
Hi everyone, I realized that when templating with helmfile template --skip-deps the dependencies added in the helmfile.yaml file are not skipped.
I have found this open issue https://github.com/helmfile/helmfile/issues/1317, and I have seen this piece of code in chartify.go//github.com/helmfile/chartify/blob/31fe0cba35ae1a33ea40e2ae40fe22052693786e/chartify.go#L364-L391>
if you take a look there, we can modify the if condition. This will fix the issue:
if u.SkipDeps && len(u.AdhocChartDependencies) == 0 -> if u.SkipDeps || len(u.AdhocChartDependencies) == 0
The thing is: do we expect this behavior?
I mean, helm dep update will never update the dependencies inside the helmfile.yaml, so maybe we can create a new parameter like –skip-release-deps
The GitHub issue comments are the right place for that discussion. Also, you can tag @mumoshu as the helmfile maintainer.
2024-02-18
New feature
• add suppress output line regex support by @yxxhero in #1329
helmDefaults:
suppressOutputLineRegex:
- "helm.sh/chart"
- "app.kubernetes.io/version"
repositories:
- name: ingress-nginx
url: <https://kubernetes.github.io/ingress-nginx>
releases:
- name: ingress-nginx
namespace: ingress-nginx
chart: ingress-nginx/ingress-nginx
version: {{ env "SUPPRESS_OUTPUT_LINE_REGEX_INGRESS_NGINX_VERSION" | default "4.8.3" }}
2024-02-19
Hello, just wondering what strategies people use to make sure that charts/releases are deployed before others?
I use sub helmfiles to group charts by functional area and use a numeric naming convention to ensure that dependent charts are deployed first but I’d like to make sure that dependent charts get updated first (potentially with a specific chart version) so that there’s no race conditions on starting pods.
Would using the helmDefault wait on the dependent charts mean that Helmfile would not proceed until those charts resources have been changed?
use needs https://helmfile.readthedocs.io/en/latest/#dag-aware-installationdeletion-ordering-with-needs
Unfortunately needs doesn’t work when the releases are split across multiple helmfiles
https://github.com/helmfile/helmfile/issues/1165
It also could be achieved with labels/selector (this way we define so called dependency tiers). But to apply configurations we need several sequential helmfile apply commands. I don’t like it much, however we sometimes have to do it this way. We also use needs, but for other purposes (even though somewhat similar)
2024-02-26
2024-02-28
Hello everyone. I have a question about helmfile. I hope you can help me
Is there a way to tell helmfile to override the values coming from the helm chart instead of merging them ?
Typically I have something like
parent:
value1: toto
value2: tata
in the default values.yaml of the chart
In my helmfile config I defined something like
parent:
value3: titi
The end result is something like
parent:
value1: toto
value2: tata
value3: titi
The only solution I found is to explicitely set the parent chart values to undefined like :
parent:
value1:
value2:
Is this the way to go ?
Another detail. In my case if I run a helmfile write-values I only see the values from the helmfile config. Not the one coming from the chart. But in my using helmfile template I can see that it uses the values from the chart. Which is very unintuitive.
helmfile version v0.162.0
@Bastien you might need to provide more info on what you’re trying to achieve as it’s not clear why you would want the behaviour you describe.
At the end of the day, the values are just a map of values, it’s what you do with them in your chart that matters. So you can implement conditional logic to select the appropriate value.
But equally, value3 is not value1 or value2 so merging them should be fine. If you really want overwriting, then pass value1 or value2 in from the helmfile config too.
Thank you @CraigB for the answer.
Yes actually I’m currently testing helmfile at my work. I was planning to use the values.yaml hosted in our chart repository as a sort of example configuration with comments describing what we can set in it. So value1 and value2 in my use case are not wanted because in my chart in this case I will iterate on the values under parent to create new k8s deployments manifest.
And do you have an idea why we don’t see the values coming from the chart when we run helmfile write-values. I understood that this command was computing the merged values file, so I was expecting to see the one coming from the chart too.
@Bastien Sorry I’m not familiar with write-values