helm: Wrong interpretation of Zero in templates files when having a default value

This is still an issue with helm v3.12.3. Can you please re-open this?

Here’s another option:

{{ if not (kindIs "invalid" .Values.MyValue) }}{{ .Values.MyValue }}{{ else }}{{ 10 }}{{ end }}

Source: https://github.com/Masterminds/sprig/issues/53#issuecomment-483414063

I had to use it because some properties like maxSurge can be an integer or a string.

For anyone looking for another way of doing this, here is how i solved it, where the absence of replica means its not a float kind:

{{ if kindIs "float64" .replicas }}{{ .replicas }}{{ else }}{{ $.Values.defaultReplicas }}{{ end }}

For anyone looking for another way of doing this, here is how i solved it, where the absence of replica means its not a float kind:

{{ if kindIs "float64" .replicas }}{{ .replicas }}{{ else }}{{ $.Values.defaultReplicas }}{{ end }}

This workaround does not work when you pass values from cli

This same thing happens in if statements with 0 values. Because of this, I can’t find a way to differentiate between a null value and a numerical zero. In my use case, the 0 is a valid value, so I need to treat it differently than the null case.

I would be able to work around it if I could explicitly check for a numeric zero value, but the things I’ve tried throw an error or don’t evaluate correctly:

With MyValue: 0:

• {{- if (eq 0 .Values.MyValue) -}} throws an “incompatible types for comparison” error, even when specifically casting the value as an int in the values file
• {{- if empty .Values.MyValue -}} evaluates to true
• {{- if (eq 0 (int .Values.MyValue)) -}} appears to work, but breaks the logic for the null case

Any suggestions?

It looks like isNil would do what I need, so I can work with that. Totally understand that it would be an easier fix than dealing with a breaking change. Thanks!

I’d like to be able to create an optional integer variable that can be explicitly set to zero.

I would usually define it something like this:

{{- if .Values.myVariable }}
option={{ .Values.myVariable }}
{{- end }}

In this case currently, if myVariable: 0 is defined, option will not be added because the if statement is evaluated as false.

Desired: If I set myVariable: 0, I’d like to have option=0. To not add the option, I would set myVariable: null, which should leave it out of the template file.