Open Networking Summit Europe 2019

While the majority of the K8s managed workloads are traditionally more forgiving towards frequent context switches, sharing CPU cores, over-provisioning, etc.; these are not the only applications which would like to leverage the features of a K8s infrastructure.

K8s resource management community tried to address this issue with the introduction of the CPU manager feature, but even the existing policies have unaddressed gaps.

The talk lists the requirements still missing from the core CPU Manager component, like the absence of sub-node level CPU pools, the true physical isolation of K8s and non-K8s managed processes, process-level CPU pinning, socket alignment, etc.

The talk then introduces an existing open-source component called CPU-Pooler and showcases how can all of these requirements satisfied today in a cloud-native, and future proof way.