starlingx/docs
Code Issues Proposed changes

Incorrect QoS Class mentioned in example of Kubernetes CPU Manager topic

Browse Source 
Updated topic "Use Kubernetes CPU Manager Static Policy with application-isolated cores"

Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: I6558b785cea772764825d0ba7572314e7bf743d0
This commit is contained in:
Juanita-Balaraj
2021-09-14 12:25:27 -04:00
parent 6ec4d277bb
commit fa10769efc
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/usertasks/kubernetes/use-application-isolated-cores.rst
View File

@@ -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 <resources:limits:cpu/memory>
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: