#helmfile - August 2023

Hi forks! https://kcl-lang.io/docs/user_docs/guides/working-with-k8s/mutate-manifests/helmfile-kcl-plugin Let me introduce you to the helmfile KCL plugin, which allows you to write KCL code in helmfile.yaml to edit or validate existing help charts. In addition, KCL is a configuration language mainly targeting Kubernetes scenarios, and its documentation is here. Welcome to provide feedback ❤️

Helmfile releases define a chart and a version. For those of you who use a single helmfile across multiple environments (dev/prod for example), how are you managing your chart between environments? As an example, dev and prod might both use chartA at version 0.1.0. When chartA is updated by the chart maintainer to 0.1.1, you may want to test 0.1.1 on dev but not on prod. How do you handle this case? One possible solution is using go templates in the helmfile.yaml, i.e.

  - name: my-release
    namespace: my-namespace
    chart: chartA
    {{ if prod }}
    version: 0.1.0
    {{ else }
    version: 0.1.1
    {{ end }}

(it is not valid syntax, but you get the idea)

Does anyone use a solution other than that? If so, can you describe your solution?

Hello,
We are trying to understand how we can override the helm values.
For example, we have a helmfile like this declared in the components:
releases:
- name: kyverno
namespace: kyverno
labels:
kubernetes.io/metadata.name: kyverno
chart: kyverno/kyverno
version: 2.6.5
values:
- kyverno_values.yaml

And then in the kyverno_values.yaml:
podLabels:
domain: appli
productname: kyverno


How can we modify the labels with stacks? We tried like this but with no efect:

components:
helmfile:
kyverno:
vars:
podLabels:
domain: test
productname: kyvernotest

We would like to apply the modified lables when we install the kyverno for that stack " atmos helmfile apply kyverno -s dienv"

Is there a reason the roboll/helmfile repo isn't archived? That would fix SEO and prevent people creating new issues in the wrong repo