-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
4.16, 4.18, 4.17
-
None
-
Quality / Stability / Reliability
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
- Proposed title of this feature request
Nice the `kube-apiserver` process to higher priority than default 0
- What is the nature and description of the request?
Control plane `kube-apiserver` process runs as default 0 niceness, meaning it's operating at same priority as most default workload processes
- Why does the customer need this? (List the business requirements here)
Clusters running OCP-VIRT workloads on bare-metal control plane nodes are contending with critical core OCP components causing nodes flapping NotReady
- List any affected packages or components.
`kube-apiserver` is 0 niceness, compared to other critical core OCP processes, for example `etcd` is -19 and `ovs-vswitchd` is -10 niceness
This is becoming more noticeable as OCP-VIRT usage increases and clusters are using schedulable control plane nodes where VM workloads are running.