since 4.12 we have the NOHZ_FULL kernel argument added by default and that somehow triggers throttling if quota not disabled

remove quota only in cases, when:

CPU manager runs with the static policy
The pod has guaranteed QoS
The container requested whole CPUs

4.12 with apps using Sriov pod has guaranteed QoS

1.
2.
3.

In theory setting CPU CFS quota for CPU pinned pods should not affect performance, but in practice it does cause performance degradation due to the (buggy) way that CFS quota are implemented in the Linux kernel.I think the best fix would be to unset any CPU CFS quota from the pod in the CPU manager when reserved CPUs (CPU sets) are assigned

the pod should not have CFS quota defined.

My understanding is that if the pod is in guaranteed QoS class and requests integral number of cpus, it should not be subject to CFS quota