enable hostPID in the mps-control-daemon pod

Signed-off-by: Tariq Ibrahim <[email protected]>
NVIDIA · Nov 12, 2024 · 173cfca · 173cfca
1 parent 23334f7
commit 173cfca
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/deployments/helm/nvidia-device-plugin/templates/daemonset-mps-control-daemon.yml b/deployments/helm/nvidia-device-plugin/templates/daemonset-mps-control-daemon.yml
@@ -53,6 +53,7 @@ spec:
       {{- if $options.hasConfigMap }}
       serviceAccountName: {{ include "nvidia-device-plugin.fullname" . }}-service-account
       shareProcessNamespace: true
+      hostPID: {{ .Values.mps.enableHostPID }}
       {{- end }}
       initContainers:
       - image: {{ include "nvidia-device-plugin.fullimage" . }}

diff --git a/deployments/helm/nvidia-device-plugin/values.yaml b/deployments/helm/nvidia-device-plugin/values.yaml
@@ -150,6 +150,11 @@ mps:
   # directories.
   # Pipe directories will be created at {{ mps.root }}/{{ .ResourceName }}
   root: "/run/nvidia/mps"
+  # enableHostPID when set to true provides the pod access to the host's PID namespace.
+  # hostPID is needed for the MPS server to find its own PID via /proc/self
+  # If the gpu driver is running in the host PID namespace, it is highly
+  # recommended that you enable this option
+  enableHostPID: true
 
 
 cdi: