#helmfile - March 2023

Hi everyone!

Is there anyway that helmfile apply will do an upgrade of a release even when helm diff does not detect changes in that release?

Currently what we see is that we have a release A and B.
1. Helm diff detects changes in release A but not in B
2. We get the information that release A is updated from helm diff.
3. Afterwards, we get the output in terminal "Affected releases are: B Updated"
4. Checking the cluster afterwards in helm list - we can see the version number has incremented for both releases

Hey guys!

Is there anyway to "package" a helmfile? It's already possible to point to a remote helmfile, but what I'd like to do is to add some custom manifests into it (like argocd application, config file, etc), but I'm not sure what's the best way to achieve that. The simplest way I can think of would be to just write all those manifests into the helmfile itself, but looking at the full helmfile specification I don't think it's possible to do that.

Hi everyone,

As a part of the automation pipeline, I generate stateValues.yaml , and my helmfiles located in helmfile.d/ . But when I run apply or template, I got this error:

helmfile --state-values-file stateValues.yaml template -e asa -l app=kubeflow-core -i --skip-deps
in helmfile.d/00-cluster-addons.yaml: environment values file matching "stateValues.yaml" does not exist in "."

As I understand, it happens because the working directory changed to helmfile.d/ when Helmfile proceeded multiple helmfiles, but my stateValues.yaml locates in the root folder, so Helmfile tries to find helmfile.d/satetValues.yaml and fails, because a path to this file is relative.

My question: is there any applicable solution for this issue, besides providing a state values file as ${PWD}/stateValues.yaml ? Maybe some change of folders structure (environments, bases, helmfile.d) may help?

I’ll be glad to hear any advice.

Hi. A question about the helmfile’s get function. I’m wondering if it supports nesting. For example if I want to use as default a value of .Values.myAnotherValue , but if this doesn’t exist - some another default. Couldn’t figure out the syntax. The naive assumption would be something like:

myVal: {{ .Value | get "myValue" (get "myAnotherValue" "1" ".Value") }}

But it definitely won’t work.
Or what would be a proper way to achieve something like this?

where can I find docs explaining all the ways to use ref+ strings? I want to try and use them to refer to a non-secret file.

It here a way in helmfile.yaml to set --skip-crds for one specific deployment? I have one chart deployment that includes CRDs that won't be needed in my case, but rest of deployments in the same helmfile must install crds.

I'm just getting started with Helmfile. I have this basic helmfile:

releases:
  - name: argo-cd
    namespace: argocd
    chart: ../../../charts/argo-cd/5.23.3
    values:
      - ./values.yaml

The ArgoCD charts exists locally on my filesystem. When I run helmfile template I get:

Building dependency release=argo-cd, chart=../../../charts/argo-cd/5.23.3
in ./helmfile.yaml: [building dependencies of local chart: command "helm" exited with non-zero status:

PATH:
  helm

ARGS:
  0: helm (4 bytes)
  1: dependency (10 bytes)
  2: build (5 bytes)
  3: ../../../charts/argo-cd/5.23.3 (30 bytes)

ERROR:
  exit status 1

EXIT STATUS
  1

STDERR:
  Error: no repository definition for <https://dandydeveloper.github.io/charts/>. Please add the missing repos via 'helm repo add'

COMBINED OUTPUT:
  Error: no repository definition for <https://dandydeveloper.github.io/charts/>. Please add the missing repos via 'helm repo add']

Is Helmfile not able to resolve transitive dependencies? Do I need to specify this manually?

dandydeveloper is a dependency of the ArgoCD Helm chart

Can the repo be added automatically by Helmfile?

Is Helmfile not able to resolve transitive dependencies? Do I need to specify this manually?

it's helm, not helmfile.

ok

Hi All

welcome

dose helmfile work with argocd?

yeah.

is there plugin ?

Hello,

I have the problem that when I use helmfile --environment k8s-dev diff --suppress-secrets I still see my provided secrets (via vault) in the output:

loki:
  storage_config:
    aws:
      bucketnames: k8s-{{ .Environment.Values.envPrefix }}-loki
      endpoint: <http://s3.eu-central-1.amazonaws.com|s3.eu-central-1.amazonaws.com>
      region: eu-central-1
      access_key_id: <ref+vault://secret/cluster-logging/{{> .Environment.Values.envPrefix }}/aws/s3?proto=https#/aws-access-key-id
      secret_access_key: <ref+vault://secret/cluster-logging/{{> .Environment.Values.envPrefix }}/aws/s3?proto=https#/aws-secret-access-key
      insecure: false
      sse_encryption: false
      s3forcepathstyle: true

I thought --suppress-secrets should hide them?

Hi there, i try to get started with helmfile.
is there a way to add individual yaml resources to a helmchart in helmfile? I tried to add a new (dummy)release and just referenced a normal subfolder with some yamls files. - in fact that worked.

repositories:
- name: cilium
  url: <https://helm.cilium.io/>
releases:
- name: cilium
  namespace: mgmt-cni-cilium
  chart: cilium/cilium
  version: 1.13.0
  values:
    - values.yaml
- name: resources
  chart: ./resources
  values:
    - values2.yaml  # <-- does not work :(

My next problem is: how can i use dynamic values with gotmpl on that subfolder? ( not realy a chart more like a bunch of gotmpl-yamls )
I noticed that {{ .Values.foo }} is not available in this subfolder release but something like {{ requiredEnv "NAME" }} dos work.
thanks for the help

https://github.com/helmfile/helmfile/releases/tag/v0.152.0 released. please enjoy it.