helm: fix vendor.dcgm.enabled: false has no effect

[shravyavorugallu]

Fixes #210

Root Cause

The vendor.dcgm.enabled helper in _helpers.tpl used Sprig's ternary function via a pipeline:

{{- ($vendor | dig "nvidia" "dcgm" "enabled" false) | ternary "true" "" -}}

When vendor.nvidia.dcgm.enabled: false is set, dig returns a Go bool(false). Sprig's ternary reflects this value and can evaluate it as truthy, causing DCGM prolog/epilog ConfigMap refs to always be injected into the Controller CR.

This breaks CPU-only deployments (minikube, non-GPU nodes) because the operator tries to reconcile DCGM prolog scripts that were never created.

Fix

Replace ternary with a native Go template if block, which correctly evaluates boolean false as falsy in all Helm versions:

{{- if ($vendor | dig "nvidia" "dcgm" "enabled" false) -}}
true
{{- end -}}

The rendered output is unchanged: "true" when enabled, "" when disabled.

[vivian-hafener]

Good morning,

Your issue indicates that this bug is present on v1.1.0, but the root cause you present as problematic is only present on main. On v1.1.0, the logic is as follows:

{{/*
Check if DCGM integration is enabled
*/}}
{{- define "vendor.dcgm.enabled" -}}
{{- .Values.vendor.nvidia.dcgm.enabled -}}
{{- end }}

The logic in v1.1.0 was broken, which did result in vendor.dcgm.enabled: false having no effect. However, I believe that this was resolved by f1786e4 on main.

If you can confirm that that commit does resolve the behavior that you are seeing, I can look into backporting that commit to release-1.0 and release-1.1.

Best,
Vivian Hafener

[shravyavorugallu]

Hi Vivian, Thanks for the clarification, that helps. I can confirm that the behavior I’m seeing does reproduce on v1.1.0, where setting "vendor.dcgm.enabled: false" has no effect due to the logic you pointed out. I’ve also reviewed commit "f1786e4" on "main", and it does appear to address the issue. Based on that, a backport to "release-1.0" and "release-1.1" would be great. Thankyou, Shravya Vorugallu.

…

On Tue, 16 Jun, 2026, 09:09 Vivian Hafener, ***@***.***> wrote: *vivian-hafener* left a comment (SlinkyProject/slurm-operator#214) <#214 (comment)> Good morning, Your issue indicates that this bug is present on v1.1.0, but the root cause you present as problematic is only present on main. On v1.1.0, the logic is as follows <https://github.com/SlinkyProject/slurm-operator/blob/v1.1.0/helm/slurm/templates/vendor/nvidia/dcgm/_helpers.tpl#L7C1-L12C11> : {{/*Check if DCGM integration is enabled*/}} {{- define "vendor.dcgm.enabled" -}} {{- .Values.vendor.nvidia.dcgm.enabled -}} {{- end }} The logic in v1.1.0 was broken, which did result in vendor.dcgm.enabled: false having no effect. However, I believe that this was resolved by f1786e4 <f1786e4> on main. If you can confirm that that commit does resolve the behavior that you are seeing, I can look into backporting that commit to release-1.0 and release-1.1. Best, Vivian Hafener — Reply to this email directly, view it on GitHub <#214?email_source=notifications&email_token=APKSJNDTFBAFUFGT67UQ2YD5AFWLRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZSGA4DINBVGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4720844521>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APKSJNHUEX35G2L56OU4JRL5AFWLRAVCNFSNUABFKJSXA33TNF2G64TZHM4DQMZYGQ2TONZXHNEXG43VMU5TINRXGEYDAOBTHE32C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/APKSJNFTOU3ZFSJKI4F3YAL5AFWLRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZSGA4DINBVGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/APKSJNFYPSMRML3ECOJIBY35AFWLRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZSGA4DINBVGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>