#helmfile - December 2021

Hi,
I am new to this channel and have a quick questions:
Can the environment values be passed to my helm charts?

Hi , I am new in helmfile . is it possible to do inherit from helmfile ? meaning that I have 1 helmfile with values and I want second helmfile to get all the data from the first one and to add some data like hooks and info

Hi All
I am trying to do simple helm config using helmfile but no success.

as mention here (overriding-values-from-a-parent-chart) I would like to provide one parent configuration and override release value.

this is a release configmap charts/microservice-a/templates/configmap.yaml

apiVersion: v1
kind: ConfigMap
metadata:
  labels: {{- include "microservice-a.labels" . | nindent 4 }}
  name: {{ include "microservice-a.fullname" . }}-config
  namespace: {{ .Release.Namespace }}
data:
  MODEL.EN: {{ .Values.model.en }}

this is my helmfile.yaml

releases:
  - name: microservice-a
    chart: ../charts/microservice-a
    values:
      - "../charts/microservice-a/values.yaml"
      - "./environments/{{ .Environment.Name }}/values.yaml"

and this is my environments/default/values.yaml

microservice-a:
  model:
    en: "model-en-1.0.mdl"

I found that the {{ .Values.model.en }} in the configmap can not be reslove.

What am I doing wrong ?

Greetings! For a long running hook command (like watching a canary progress) is it possible to stream logs in some way? Currently it seems the logs are only output once the hook completes.

Hi, I would like to have some recommendations, since we want to integrate helmfile in our deployment process...

Our infrastructure has following details:

• we have many customers
• all customers have the same installed services (each customer get's it's own services, no sharing between customers)
• credentials are different for all customers
• we have seperate deployment process (we dont want to upgrade all customers at the same time)
• all customer-config data is seperated into seperate config files, like:
• -> config/customer1.yaml
• -> config/customer2.yaml
• -> config/customer3.yaml
So I'm wondering, if we should use "Environment" with the customer name, to upgrade it.. or would you recommend another variable?
And do you think it's better to create multiple helmfiles for this process, or just one? Thank you!

hi folks! Thanks so much for creating helmfile - it is one of the most useful tools on the SRE team i’m on. QQ - any plans to start releasing a darwin arm64 (m1 mac) build?

Hi, how is this PR supposed to work? https://github.com/roboll/helmfile/pull/1745

I’ve just come across this tool which seems to be an alternative to helmfile.
https://github.com/helmwave/helmwave

Hmm. Look definitively nice, but have everything in helmfile already. Only real plus is multi environment at once

I don’t see alternative to helmfile’s needs.