#helmfile - May 2022

I'm using helmfile to install a chart that I've written myself. Currently, I keep all of my values files in the same directory as my helmfile.yaml, and the chart itself has no values files (just templates/ and a Chart.yaml ).

❓️ Should some of the values live in the helm chart, or does it make sense to keep them all alongside the helmfile like I'm currently doing?

hello new here 👋

so im here particularly seeking a special alternative to helm upgrade --recreate-pods which got removed in helm3. issue
but helmfile seems to be supporting in the helmfile.yaml , example code

recreatePods: true

does that work for helm3 , if yes how?
the source code in pkg/state/state.go is just passing on the flag, and not doing anything else. it won't work with helm 3 right? it doesn't when i do from helm3 's cli.

the actual problem im trying to solve is, in case if you can help this directly:
• im creating helm-as-a-service (by wrapping helm3 binary behind a fastapi server), for deployments via API. similar to this and this project, where there'd be frequent need to refresh, soft-restart (graceful replace old with new) the pods by pulling fresh image and doing rollout and no values.yaml changes.
◦ if you thought kubectl rollout restart svc/blah-blah would work, im thinking same. but helm install release chart 's release and chart name exactly don't match the kubectl pod name. also there might be lot of too many pod replicas and pod dependencies as well.
• the best thing i could have is:
◦ 1. helm command for soft-restarting a release (with chart dependencies)
◦ 2. helm command for soft-restarting a release (without chart dependencies).
but they don't exist. 🥲

thanks if you read this far!

I’ve noticed that the latest version of helmfile in roboll/helmfile is 0.144.0 whereas in helmfile/helmfile it’s 0.143.4. @mumoshu What would be the harmonisation process? Will we have the continuation of the existing versions in helmfile/helmfile or what is the release strategy? Thanks!

Can’t find if there is a possibility in helmfile to create a helm release out of remote plain kubernetes manifests. As far as I remember there were some discussions regarding variantdev/chartify, however since there is no readme there I can’t recall if I’m on the right track. Some features were definitely added to helmfile, though I can’t find anything except for working with kustomizations. Am I missing something?

Just a short question:
Is it possible to have needs between releases defined in separate sub-helmfiles?

Is it possible to insert the current FQDN of the node I’m currently executing the helm chart install on inside the templates helm chart?

are there any high-level goals for documentation for this project?
i’ve started implementing this at my workplace and while there’s a ton of functionality, some of the documentation is outdated or hard to find.
i’d be glad to contribute to this, but want to know if there’s any existing goals for this already

Does anyone have a good explanation on helm and helmfile for beginners?

I'm willing to create something, but not if it's already done 🙂

Hi , In my application each micro service has different livenessProbe configuration.
is there any way to pass complete livenessProbe configuration from values.yaml to deployment template file?

What does CloudPosse use by default for k8s ingress controller?

what’s the best way to install something like the knative-operator that doesn’t have a helm chart? official knative docs push users to manually apply

kubectl apply -f <https://github.com/knative/operator/releases/download/knative-v1.4.1/operator.yaml>

helmfile hooks look messy. trying to find an example of “Ability to install a directory of K8s manifests as a chart” as mentioned in this PR

Hi , my project consists of 11 micro services . we have created templates and helmfile to deploy.
Total we have 11 values.yaml corresponding to 11 releases in the helmfile per environment.
we want to build ci/cd to deploy into multiple environments sequentially .
What is best approach we can follow to deploy into multiple environments?

helmfiles:
{{- if (.Values | get "enable_test_secret" true) }}
  - path: releases/-secrets/helmfile.yaml
{{- end }}

Excuse me. is it right? Thanks very much. it is in main helmfile.

Hi there how to template helmfile so it will check is it first install or upgrade

<.Release.Revision>: can’t evaluate field Revision in type state.releaseTemplateDataRelease
Any how i can get Relese.Revision from helmfile to manipulate with args?