-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
I'm not sure what exactly is the "best-effort CPU Manager policy" in the 4.18 release notes' Known Issues section.
It says: "As a workaround, schedule a pod with a best-effort CPU Manager policy on the affected node."
The CPU Manager only has none and static policies, so I suspect this might actually be referring to the best-effort QoS.