#helmfile - July 2024

forswearbeetle
forswearbeetleover 2 years ago
Hello, I created article integrating ory product with my K8S cluster and istio using helmfile, I would appreciate your feedback
https://hamzabouissi.github.io/posts/guardians_of_hell/
RickA
RickAover 2 years ago
I've got a dependent chart with a helper file with:

{{- define "dep.environment" -}}
{{ (.Values.common | default (dict "envName" "DEFAULT")).envName }}
{{- end -}}

Which works super as long as .Values.common.envName has a value. I can't figure out a config that works when it doesn't have a value. The default never kicks in.

Have tried dig, and ((.Values.common).envName) | default "default") and a few other methods. In fact the example with default I just listed works if I move it into the deploy directly instead of the dependent chart. So what format works properly in a dependent chart, if any?
Jason
Jasonover 2 years ago
Hey I recently wrote this blog post on how painful it was to write a Helm Deployment and Kubernetes Objects using Go: https://theclouddude.co.uk/the-painful-journey-of-deploying-a-helm-chart-to-kubernetes-with-go
Apacuka
Apacukaover 2 years ago
Is there a way I can build a variable inside release scope before rendering it? Or create some kind of self-reference?
Ondrej Jombik
Ondrej Jombikover 2 years ago
Hello, my Helmfile is version v0.144.0 and set-string: should be available since v0.144.0.
However, when I try to use it I get this error:
⨠ helmfile lint
in ./helmfile.yaml: failed to read helmfile.yaml: reading document at index 1: yaml: unmarshal errors:
  line 23: field set-string not found in type state.ReleaseSpec

I must be doing something wrong, but not sure what