kapp-controller VS helmfile

We use kapp-controller when applying our charts (it uses helm template instead of helm install) so we can be very rigorous about what fields are changeable (like through pod autoscaling) and what are not (securitycontext, etc.)

Even further, you could describe your "fetch", "template", and "deploy" stages in akapp-controller AppCR and then you'd have a controller (like an operator) running the cluster continuously reconciling your private cloud to ensure that it's always reconverging to the desired state. This is basically what's underpinning a number of VMWare's commercial (and OSS) Tanzu offerings, as well as some other organization's internal platforms, or "self hosted private clouds"

Full disclosure: I work on https://carvel.dev/kapp-controller/ which can also continuously reconcile helm charts (via our own CRD ).

kapp-controller

kapp-controller - Capture application deployment workflow in App CRD. Reliable GitOps experience powered by kapp.

What we’re going to install into the newly created AKS cluster is located in the helm directory. The descriptive Helmfile approach enables us to define applications and their settings in the helmfile.yaml file.

Is there any alternative to https://github.com/roboll/helmfile you are currently using in your company.

Interesting, I have approached this problem using Helmfile (https://github.com/roboll/helmfile) to define a “platform release package.”

To make managing the Helm deployments a little easier I used helmfile (https://github.com/roboll/helmfile).

But in general it's always easier to keep things quite separated. Meaning in separate helm releases. If you want to be able to manage things "together" at will, then you can use helmfile ( https://github.com/roboll/helmfile )

I agree; helm is too declarative.

Whenever I can, I use helmfile[0] for storing variables for helm since it does add a declarative layer on top of helm.

0 - https://github.com/roboll/helmfile

I went through the Helmfile repo Readme to figure out the difference between helmfile sync and helmfile apply. It seems like unlike the apply command, the sync command doesn't do a diff and helm upgrades the hell out of all releases 😃. But from the word sync, you'd expect the command to apply those releases that have been changed. There is also mention of the potential application of helmfile apply to periodically syncing of releases. Why not use helmfile sync for this purpose? Overall, the difference didn't become crystal clear, and I though there could probably be more to it. So, I'm asking.

helmfile is something i’ve used in the past for this https://github.com/roboll/helmfile

I always felt like dependencies in helm are for very simple non-coupled packages. I many times use Helmfile (https://github.com/roboll/helmfile) to manage dependencies instead of banging my head with vanilla Helm.

Once you do that, learn to create dynamic helm charts that use go templating and conditionals: https://github.com/roboll/helmfile