Skip to content

Commit cece71b

Browse files
gjulianmijkaylin
andauthored
Update content/en/gpu_monitoring/setup.md
Co-authored-by: Kathy L. <[email protected]>
1 parent b843556 commit cece71b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/gpu_monitoring/setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -260,7 +260,7 @@ Additionally, to enable advanced eBPF-based metrics such as GPU core utilization
260260

261261
## Set up GPU Monitoring on a mixed Kubernetes cluster
262262

263-
In a mixed cluster, some nodes have GPU devices while other nodes do not. Due to the way that the NVIDIA device plugin for Kubernetes works, the Agent needs to have a specific runtime class to access the GPU devices that is only present on GPU nodes. Therefore, two separate DaemonSets, one for the runtime class in GPU nodes, and another for non-GPU nodes, are required.
263+
In a mixed Kubernetes cluster, some nodes have GPU devices while other nodes do not. Two separate DaemonSets are required (one for the runtime class in GPU nodes, and another for non-GPU nodes) due to runtime class requirements for the NVIDIA device plugin for Kubernetes.
264264

265265
The recommended method to set up the Agent in this case is using the Datadog Operator, version 1.20 or greater, which provides features to make this setup easier. However, for compatibility reasons instructions are also provided for Helm installations or for older versions of the Datadog Operator.
266266

0 commit comments

Comments
 (0)