#helmfile - April 2022

Helmfile has officially forked!

https://github.com/helmfile/helmfile

Anyone uses helmfile just for templating?

Currently I have a monochart repository where all my apps depend on. I use argocd so I only use helmfile template --output-dir to achieve gitops. Just want to ask around as to how other people have been doing it!

Erik/Cloudposse has influenced me to move my standard helm charts (karpenter, external-dns, etc) to terraform helm. 😅 Helmfile is only for having a declarative config for templating my apps.

@mumoshu are you going to move the terraform-provider-helmfile to the new org?

Helmfile needs a logo! I'm always struggling for something on our slides. 😃

This is my crude hack.

Hi thanks for the lib! I need to use the output of a.yaml.gotmpl in b.yaml.gotmpl. How can I do that? The "layering" feature seems promising but I fail to use it even for official examples (https://github.com/roboll/helmfile/issues/2128)

I do love me some helmfile! Quick mockup in adobe illustrator :p

grr, I'll throw it in photoshop later and get that white outline out of the way lol

this might work...

weird, it isn't showing in illustrator lol. Oh well, I've shown enough of my noobness for one day 😛

I like it!

Thanks! I just watched your "Effortless Helm Deployments" talk for codefresh! Helped a lot!

Hahah wow that was like 3 years

Yeah man, I haven't been able to find a ton of recent k8's-related learning material. Probably just not googling the right stuff. The cloudposse repo is a good SoT, i've found, if you're looking for a quick "best practices" reference.

I am curious though; what are some of the new/exciting things in k8's-land in 2022? I was looking into Cluster API - that's super exciting.

Hi folks, thanks for creating helmfile - it's a great tool to manage multiple charts!
I had a question about the needs parameter for specifying dependencies. The documentation recommends arranging helmfiles by microservice or by team. In our case we have multiple teams, with each team owning multiple microservices. The needs param works fine when service A depends (or needs) service B and both A and B are owned by the same team. If A needs B it's simple to use needs in A's release declaration in the same helmfile.

However, let's say there is service C which is owned by another team, and C depends on A's APIs. The needs param does not work across helmfiles (even when the kubecontext/namespace prefix is specified)

Whats is the recommended layout in such cases? One not so great approach would be a giant helmfile with everything inside it.

👋 Hello, team! I am trying to use Helmfile to install resources based on some CRDs that we created. But the CRD kind resources themselves have a specific order of installation and un-install is just reverse. How can I have a specific the order of install and un-install with Helmfile?

Hi guys! Does anyone know if everything helmfile provides is also possible with flux2 ? Mainly speaking in terms of templating, orchestrating…

any one using https://github.com/FairwindsOps/reckoner instead of helmfile?

Hey guys
I'm trying to embed my daemonset yaml file into the public filebeat helm chart from github but I'm struggling. Can anyone assist me?