Update k8s-best-practices-cpu-manager-pinning.adoc

Author: mwlinca

modules/k8s-best-practices-cpu-manager-pinning.adoc

@@ -12,9 +12,14 @@ Workload Requirement: If a workload is doing CPU pinning, exec probes may not be
 
 See test case link:https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md#networking-dpdk-cpu-pinning-exec-probe[networking-dpdk-cpu-pinning-exec-probe]
 
-**Impacts and Risks of Non-Compliance:** Exec probes on CPU-pinned DPDK workloads can cause performance degradation, interrupt real-time operations, and potentially crash applications due to resource contention.
+**Impacts and Risks of Non-Compliance:** Exec probes on CPU-pinned or DPDK workloads can cause performance degradation, interrupt real-time operations, and potentially crash applications due to resource contention.
 
 [IMPORTANT]
 ====
+Important note on using probes: If the CNF is running a DPDK process, do not use exec probes (executing a command within the container) as it may pile up and block the
+node eventually.
+
+Workload Requirement: If a workload is doing CPU pinning, exec probes may not be used.
+
 Workloads MUST NOT apply tolerations for NoExecute, PreferNoSchedule, and NoSchedule
 ====