Skip to content

Commit 8afdc69

Browse files
authored
Update k8s-best-practices-cpu-manager-pinning.adoc
1 parent 48a8c7b commit 8afdc69

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@
33

44
The OpenShift platform can use the Kubernetes CPU Manager to support allocation of cores using kubernetes guaranteed QoS class for applications. Isolcpus is not enabled.
55

6-
Important note on using probes: If the workload is doing CPU pinning and running a DPDK process do
7-
not use exec probes (executing a command within the container) as it may pile up and block the
8-
node eventually.
6+
link:https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/#create-a-pod-that-gets-assigned-a-qos-class-of-guaranteed[]
97

8+
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
9+
node eventually.
1010

1111
Workload Requirement: If a workload is doing CPU pinning, exec probes may not be used.
1212

0 commit comments

Comments
 (0)