Comment 0 for bug 1830634

Brief Description
-----------------
isolcpu's does not play nice with besteffort or burstable pods.

With isolcpu's enabled these pods will get stuck on the core where they were first scheduled vs floating. Overlaying exlusive cpu's with this, one can end up in a situation where the besteffort/burstable pods are running on the same cpu as the exclusive pods.

There will always be some besteffort or burstable pods on a worker node as the system pods (calico et) fall into the category.

Severity
--------
Major

Steps to Reproduce
------------------
Launch pods with exclusive CPU's

Expected Behavior
------------------
Pods using defaultCpuSet should be able to float across that set

Actual Behavior
----------------
See description

Reproducibility
---------------
100%

System Configuration
--------------------
Low-latency worker

Branch/Pull Time/Commit
-----------------------
 BUILD_DATE="2019-05-24 17:42:34 -0400"

Last Pass
---------
Never

Timestamp/Logs
--------------
N/A

Test Activity
-------------
Other