Customers have asked MicroShift to support OCP's workload partitioning feature.

https://github.com/openshift/enhancements/blob/master/enhancements/workload-partitioning/management-workload-partitioning.md is the original design document describing the feature in single-node OCP.

https://github.com/openshift/enhancements/pull/1213 is a follow-up design extending support to multi-node clusters.

https://github.com/openshift/enhancements/blob/master/enhancements/shared-and-guaranteed-cpu-pools.md talks about splitting the CPU pool between "shared" and "guaranteed" segments.

At the very least, we would need to incorporate the pod mutating webhook, a flag to enable it, the kubelet and cri-o settings, and documentation to tie it all together.

The goal of workload paritioning is to be able to limit the amount of CPU usage of all control plane components. E.g. on a 8 core system, we can limit and gurantee that the control plane is using max 2 cores.

This is NOT the same as support low latency workload. see https://issues.redhat.com/browse/OCPSTRAT-361 for that.