#helmfile - November 2023

QQ, are helmDefaults inherited into sub-helmfiles or do they need to specify the defaults again?

Initial impl of a pulumi provider https://github.com/helmfile/vals/pull/180

@mumoshu currently any use of insecureSkipTLSVerify which calls helm diff upgrade fails (e.g., helmfile apply with helmDefaults.insecureSkipTLSVerify: true), see https://github.com/databus23/helm-diff/issues/503 . (I’m not sure if it worked previously.)

Hi guys

I run helmfile to deploy the same thing in kubernetes and on vm. They have the same avaliable memory(~3.5Gi) but CPU can vary. On VM it’s 2 cores on kubernetes request is only 700m without limit.
In many cases job that is running in kubernetes get OOM meanwhile it works without problems on VM.
command: helmfile sync

It seems to me that problem could be related to CPU(in bad case helmfile can only get 700m) and disk usage(other pods on the same node can use disk) but I have no idea how that resulted in OOM kill, could someone explain how these things can be related?

Is there any way to get a deterministic group ID from the DAG during installation? I was hoping to use it as an annotation

I notice that passing in a namespace on the command line takes precedence over any namespace value defined in a release. Is there any way to control this behaviour? i.e. I want to enforce a release is only installed in a specific namespace

Hey there, I have a very small helmfile with which I want to sync releases in different environments, currently it looks like this:

environments:
  default: # developers and jenkins commit deployments
    values:
      - default:
          enabled: true
      - live:
          enabled: false
  live: # jenkins only, live deployments
    values:
      - default:
          enabled: false
      - live:
          enabled: true
---
templates:
  default:
    chart: ./chart
---
releases:
  - name: dev-release
    condition: default.enabled
    inherit:
      - template: default
  - name: live-release
    condition: live.enabled
    inherit:
      - template: default

is this the correct way to do this? Or is there a better way?