From fa10769efc3e390bb359811ff1058b60f4a0d5b3 Mon Sep 17 00:00:00 2001 From: Juanita-Balaraj Date: Tue, 14 Sep 2021 12:25:27 -0400 Subject: [PATCH] Incorrect QoS Class mentioned in example of Kubernetes CPU Manager topic Updated topic "Use Kubernetes CPU Manager Static Policy with application-isolated cores" Signed-off-by: Juanita-Balaraj Change-Id: I6558b785cea772764825d0ba7572314e7bf743d0 --- .../usertasks/kubernetes/use-application-isolated-cores.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/usertasks/kubernetes/use-application-isolated-cores.rst b/doc/source/usertasks/kubernetes/use-application-isolated-cores.rst index b6935ab2a..2c62d95ee 100644 --- a/doc/source/usertasks/kubernetes/use-application-isolated-cores.rst +++ b/doc/source/usertasks/kubernetes/use-application-isolated-cores.rst @@ -33,7 +33,7 @@ dedicated/pinned) to the pod. application-isolated cores are NOT supported with **Guaranteed QoS** class. Specifically this requires either: - - for **Best Effort**, do NOT specify resources:limits:cpu/memory> + - for **Best Effort**, do NOT specify or @@ -85,7 +85,7 @@ dedicated/pinned) to the pod. .. note:: The nodeSelector is optional and it can be left out entirely. In which - case, it will run in any valid note. + case, it will run in any valid node. You will likely need to adjust some values shown above to reflect your deployment configuration. For example, on an AIO-SX or AIO-DX system. @@ -114,7 +114,7 @@ dedicated/pinned) to the pod. CPU details per core: #. Describe the pod or node to see the CPU Request, CPU Limits and that it is - in the "Guaranteed" QoS Class. + in the "Burstable" QoS Class. For example: