Skip to content

Commit 63327bf

Browse files
authored
Apply suggestions from code review
1 parent ade5b7a commit 63327bf

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/en/gpu_monitoring/setup.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,15 @@ This page provides instructions on setting up Datadog's GPU Monitoring on your i
88

99
To begin using Datadog's GPU Monitoring, your environment must meet the following criteria:
1010

11-
- You are a Datadog user with active Datadog infrastructure hosts. If not, see the following guides:
11+
- You have a Datadog account and are running the Datadog Agent on your infrastructure hosts. If not, see the following guides:
1212
- [Install the Datadog Agent on Kubernetes][1]
1313
- [Install the Datadog Agent on Docker][7]
1414
- [Install the Datadog Agent on non-containerized Linux][8]
1515
- The NVIDIA drivers are installed on the hosts. If using Kubernetes, the NVIDIA device plugin for Kubernetes is installed ([directly][3], or through [NVIDIA GPU Operator][4])
1616

1717
#### Minimum version requirements
1818

19-
- **Datadog Agent**: version 7.72.2
19+
- **Datadog Agent**: v7.72.2
2020
- **Operating system**: Linux
2121
- (Optional) For advanced eBPF metrics, Linux kernel version 5.8
2222
- **NVIDIA driver**: version 450.51
@@ -26,10 +26,10 @@ If using Kubernetes, the following requirements must be met:
2626
- [**Datadog Operator**][5]: version 1.18, _or_ [**Datadog Helm chart**][6]: version 3.137.3
2727
- **Kubernetes**: 1.22 with PodResources API active
2828

29-
## Set up GPU Monitoring on a uniform Kubernetes cluster or non-Kubernetes environment
29+
## Set up GPU Monitoring on a uniform Kubernetes or non-Kubernetes environment
3030

3131
The following instructions are the basic steps to set up GPU Monitoring in the following environments:
32-
- In a Kubernetes cluster where **all** the nodes have GPU devices
32+
- In a Kubernetes cluster where **all** nodes have GPU devices
3333
- In a non-Kubernetes environment, such as Docker or non-containerized Linux.
3434

3535
{{< tabs >}}
@@ -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 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.
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)