diff --git a/examples/datadog/agent_on_openshift_values.yaml b/examples/datadog/agent_on_openshift_values.yaml
index a95bea8c3..11d696786 100644
--- a/examples/datadog/agent_on_openshift_values.yaml
+++ b/examples/datadog/agent_on_openshift_values.yaml
@@ -1,11 +1,10 @@
-# Datadog Agent with Logs, APM, Processes, and System Probe enabled
+# Datadog Agent with Logs, APM, and Processes
 # with specific configurations to work on OpenShift 4.
 # When installing the chart, install onto a non-default namespace with
 # `helm install --namespace <your_ns>` due to existing SecurityContextConstraints
 # on the default namespace. For more details about setting appropriate security
 # constraints, see https://docs.datadoghq.com/integrations/openshift/ and
 # https://www.datadoghq.com/blog/openshift-monitoring-with-datadog/
-
 targetSystem: "linux"
 datadog:
   # apiKey: <DATADOG_API_KEY>
@@ -15,20 +14,15 @@ datadog:
   appKeyExistingSecret: <DATADOG_APP_KEY_SECRET>
   clusterName: <CLUSTER_NAME>
   tags: []
-  criSocketPath: /var/run/crio/crio.sock
   # Depending on your DNS/SSL setup, it might not be possible to verify the Kubelet cert properly
   # If you have proper CA, you can switch it to true
   kubelet:
     tlsVerify: false
-  confd:
-    cri.yaml: |-
-      init_config:
-      instances:
-        - collect_disk: true
   logs:
     enabled: false
   apm:
-    portEnabled: false
+    portEnabled: true
+    socketEnabled: false
   processAgent:
     enabled: true
     processCollection: false
@@ -49,10 +43,4 @@ agents:
 clusterAgent:
   podSecurity:
     securityContextConstraints:
-      create: true
-clusterChecksRunner:
-  enabled: true
-  replicas: 2
-kube-state-metrics:
-  securityContext:
-    enabled: false
+      create: true
\ No newline at end of file