Skip to content

Commit ade5b7a

Browse files
committed
Fix tab
1 parent 1907aa8 commit ade5b7a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/gpu_monitoring/setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -265,7 +265,7 @@ In a mixed cluster, some nodes have GPU devices while other nodes do not. Due to
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

267267
{{< tabs >}}
268-
{{% tab "Datadog Operator (>=1.20)" %}}
268+
{{% tab "Datadog Operator (1.20 or greater)" %}}
269269

270270
To set up GPU Monitoring on a mixed cluster with the Datadog Operator, use the Operator's [Agent Profiles][2] feature to selectively enable GPU Monitoring only on nodes with GPUs.
271271

@@ -350,7 +350,7 @@ To set up GPU Monitoring on a mixed cluster with the Datadog Operator, use the O
350350
[4]: https://github.com/DataDog/datadog-agent/releases
351351

352352
{{% /tab %}}
353-
{{% tab "Datadog Operator (<1.20)" %}}
353+
{{% tab "Datadog Operator (1.18 or 1.19)" %}}
354354
To set up GPU Monitoring on a mixed cluster with the Datadog Operator, use the Operator's [Agent Profiles][2] feature to selectively enable GPU Monitoring only on nodes with GPUs.
355355

356356
1. Ensure that the [latest version of the Datadog Agent][4] is [installed and deployed][1] on every GPU host you wish to monitor.

0 commit comments

Comments
 (0)