helm evaluating int(0) as null value conficts with defaults
Helm interprets 0 as a null value and uses the default.
This causes a problem in fusex (https://gitlab.cern.ch/eos/eos-charts/-/blob/master/fusex/templates/configmap.yaml#L17) where there are options we might want to set to 0 but the default is 1.
Other charts might also be affected.
A dumb workaround is to set all defaults to zero and override on the need.
Related to this issue upstream: https://github.com/helm/helm/issues/3164