updated gpum onboarding documentation when using dd-operator for k8s deployments

Author: val06

gpu/README.md

@@ -174,6 +174,8 @@ helm install -f values.yaml -f values-gpu.yaml datadog-gpu datadog
 
 #### Datadog Operator
 
+_**Minimal required operator version: 1.14**_
+
 To enable the GPU feature in clusters where all the nodes have GPUs, set the `features.gpu.enabled` parameter in the DatadogAgent manifest:
 
 ```yaml
@@ -185,6 +187,18 @@ spec:
   features:
     gpu:
       enabled: true
+# for operator versions 1.14.x and 1.15.x  add this section
+  override:
+    nodeAgent:
+      containers:
+        agent:
+          env:
+            # add this env var, if using operator version 1.14.x
+            - name: DD_ENABLE_NVML_DETECTION
+              value: "true" 
+             # add this env var, if using operator versions 1.14.x or 1.15.x
+            - name: DD_COLLECT_GPU_TAGS
+              value: "true" 
 ```
 
 For **mixed environments**, use the [DatadogAgentProfiles feature](https://github.com/DataDog/datadog-operator/blob/main/docs/datadog_agent_profiles.md) of the operator, which allows different configurations to be deployed for different nodes. In this case, it is not necessary to modify the DatadogAgent manifest. Instead, create a profile that enables the configuration on GPU nodes only:
@@ -210,6 +224,14 @@ spec:
             env:
               - name: DD_GPU_MONITORING_ENABLED
                 value: "true"
+           # add this env var, if using operator version 1.14.x      
+          agent:
+            env:
+              - name: DD_ENABLE_NVML_DETECTION
+                value: "true" 
+          # add this env var, if using operator versions 1.14.x or 1.15.x
+              - name: DD_COLLECT_GPU_TAGS
+                value: "true"
 ```
 
 <!-- xxz tab xxx -->