Skip to content

Commit

Permalink
Allow CDI annotation prefix to be specified
Browse files Browse the repository at this point in the history
This change allows the CDI annotation prefix to be specified
as a helm value and not only as an envvar.

Signed-off-by: Evan Lezar <elezar@nvidia.com>
  • Loading branch information
elezar committed Sep 30, 2024
1 parent 04e2a1c commit 5db38d5
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -169,6 +169,10 @@ spec:
- name: NVIDIA_CDI_HOOK_PATH
value: {{ .Values.cdi.nvidiaHookPath }}
{{- end }}
{{- if typeIs "string" .Values.cdi.annotationPrefix }}
- name: CDI_ANNOTATION_PREFIX
value: {{ .Values.cdi.annotationPrefix | quote }}
{{- end }}
{{- if typeIs "bool" .Values.gdsEnabled }}
- name: GDS_ENABLED
value: {{ .Values.gdsEnabled | quote }}
Expand Down
1 change: 1 addition & 0 deletions deployments/helm/nvidia-device-plugin/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -156,3 +156,4 @@ cdi:
# nvidiaHookPath specifies the path to the nvidia-cdi-hook or nvidia-ctk executables on the host.
# This is required to ensure that the generated CDI specification refers to the correct CDI hooks.
nvidiaHookPath: null
annotationPrefix: null

0 comments on commit 5db38d5

Please sign in to comment.