-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Expand file tree
/
Copy pathnvidia-device-plugin-helmchart.yaml
More file actions
44 lines (42 loc) · 1.58 KB
/
Copy pathnvidia-device-plugin-helmchart.yaml
File metadata and controls
44 lines (42 loc) · 1.58 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
# SPDX-License-Identifier: Apache-2.0
# HelmChart CR for auto-deploying the NVIDIA k8s-device-plugin via k3s Helm controller.
# This manifest is conditionally copied into /var/lib/rancher/k3s/server/manifests/
# by the cluster entrypoint when GPU_ENABLED=true.
#
# The chart installs:
# - NVIDIA device plugin DaemonSet (advertises nvidia.com/gpu resources)
#
# NFD and GFD are disabled; the device plugin's default nodeAffinity
# (which requires nvidia.com/gpu.present=true) is overridden to empty
# so it schedules on any node without requiring NFD/GFD labels.
#
# CDI injection mode: the device plugin uses deviceListStrategy=cdi-cri so that
# devices are injected via CDI hooks before container start. Sandbox pods only
# need the nvidia.com/gpu resource request — no runtimeClassName is required.
#
# k3s auto-detects nvidia-container-runtime on PATH and registers the "nvidia"
# RuntimeClass automatically, so no manual RuntimeClass manifest is needed.
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
name: nvidia-device-plugin
namespace: kube-system
spec:
repo: https://nvidia.github.io/k8s-device-plugin
chart: nvidia-device-plugin
version: "0.18.2"
targetNamespace: nvidia-device-plugin
createNamespace: true
valuesContent: |-
runtimeClassName: nvidia
deviceListStrategy: cdi-cri
deviceIDStrategy: index
cdi:
nvidiaHookPath: /usr/bin/nvidia-cdi-hook
nvidiaDriverRoot: "/"
gfd:
enabled: false
nfd:
enabled: false
affinity: null