You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are treated as default values, which mean you have to specify the exporter-metrics-volume in your values.yaml when you specify another volume because the default values are overridden.
For reference, here's my values.yaml. nvidia-install-dir-host volume is needed in my environment (ref: #385 (comment)).
Is this a new feature, an improvement, or a change to existing functionality?
Change
Please provide a clear description of the problem this feature solves
As of 3.3.9-3.6.1,
exporter-metrics-volume
configMapVolume and volumeMount is specified in values.yamlhttps://github.com/NVIDIA/dcgm-exporter/blob/3.3.9-3.6.1/deployment/values.yaml#L143-L154
These are treated as default values, which mean you have to specify the
exporter-metrics-volume
in your values.yaml when you specify another volume because the default values are overridden.For reference, here's my values.yaml.
nvidia-install-dir-host
volume is needed in my environment (ref: #385 (comment)).Feature Description
Uses don't have to specify
exporter-metrics-volume
in their values.yaml even when they have another volume.Describe your ideal solution
Moving
exporter-metrics-volume
configMapVolume and volumeMount out of values.yaml to templates/daemonset.yaml.Since
exporter-metrics-volume
is required in any case, it makes sense if we have those values in the k8s yaml itself.Additional context
No response
The text was updated successfully, but these errors were encountered: