#helmfile - June 2021

Hey @mumoshu! Long time no talk. Hope you're doing well. Curious if you'd be open to support an issue/PR to the secrets handling for helmfile. I have a scenario where my secrets are resolved externally and brought in with an exec, but I'd really like to get them able to be suppressed. I'm thinking if i could shove them into the secrets: block with a secret engine of none, I could still leverage the suppression with minimal code change?

hello all, when I do a helmfile apply and sometimes I cannot deploy all apps becaue of an error, but I see helmfile already created the "release" secret file and next file it won't try to deploy the app because it checks the file and it does not see any changes, however I could not deploy that app. is that expected, or is there a setting or param that I can set to delete this file on error / revert ?

Hey guys, recently started using helmfiles, had some questions in my head which i wanted to confirm how people here in community manage:

• I am exploring a use-case, where i want to use a public helm chart (from an open source repo) with my own values.yml file, but want to use some of my own custom templates as well (with crd's, on my local). Is there a possibility to club them together in a single helmfile -f blah.yml sync command?
• Or is it not possible and only way (and best practice) is to get a copy of the actual templates and create in-house charts?

Do you guys use helmfile and argocd together?

Has anyone had an issue with kustomize/jsonPatch after v0.139.0

What used to be a simple jsonPatch applying labels to a manifest now writes out an empty manifest

I have tried both a jsonPatch and a strategicMergePatch. If i remove the patch entirely, i get template output, if i add the patch back in i get zero output from templating

when I use jsonpatch. Is there any param or option to force helmfile to quit if the file that I would like to patch is not exists. E.g. I added the name incorrectly.

hi here! nice to meet you all. I’m a new comer to helmfile and struggling to find an elegant solution to a problem… wondered if anyone had come up with some solutions in the past.

I’ve inherited a helmfile with 100+ releases defined within. Most of the helm charts for the releases share a common values structure, except they vary in the root element name; e.g. my-app-a and my-app-b in the samples below

# chart-a/values.yaml
my-app-a:
  theCommonThing:
    theCommonSubThing: theValue
    mySpecialThing: mySpecialValue

# chart-b/values.yaml
my-app-b:
  theCommonThing:
    theCommonSubThing: theValue

With DRY in mind, I’m trying to find a way of defining some common values and apply them to the helmfile releases that inherit this structure. For example, using the charts above, I’d like to override theCommonThing.theCommonSubThing for multiple releases, without affecting theCommonThing.mySpecialThing.

The standard approach of layering the values doesn’t quite work because each helm chart has a different root value… and I don’t believe I can target or wildcard this.

Without updating the 100s of helm charts, the best solution I can think of it to introduce a convention in my helmfile where .Release.Name = root node name and then use {{ .Release.Name }} as the root node in a shared values file.

#common.yaml.gotmpl
{{.Release.Name}}:
  theCommonThing:
    theCommonSubThing: theOverridenValue

#helmfile.yaml 
releases:
  - name: myRelease
    values:
      - common.yaml.gotmpl
      - my-app-a:
          theCommonThing:
            mySpecialThing: myOverridenValue

However I’m as little apprehensive about hijacking the release name for this purpose.

Feels like I should be able to use templating or yaml anchors to solve this, but helmfile is quite specific about what can be templated. Interested to hear if anyone else has hit a similar challenge…

I wrote this recently:
• https://joachim8675309.medium.com/devops-tools-introducing-helmfile-f7c0197f3aea

I was deploying ClusterIssuer kind in helmfile using raw helm chart, and I got this:

STDERR:
  Error: Internal error occurred: failed calling webhook "<http://webhook.cert-manager.io|webhook.cert-manager.io>": Post "<https://cert-manager-webhook.kube-addons.svc:443/mutate?timeout=10s>": dial tcp 10.0.31.194:443: connect: connection refused

Code is from:
• https://gist.github.com/darkn3rd/594e5ddcf27fe577e04e356884cf7e54
My question, is how do I try this again, Everytime I do helmfile apply, it does nothing. I don't see the anything updated after the failure, and helm ls gives:

Comparing release=cert-manager-issuers, chart=itscontained/raw