-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Last Level Cache locality for MicroShift
-
Product / Portfolio Work
-
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
Not Selected
-
None
-
None
-
None
Epic Goal
- Support the prefer-align-cpus-by-uncorecache CPUManager feature on MicroShift, as proposed at agreed upon Enhancement Proposal (TBD)
Why is this important?
- Modern CPU have multiple last level caches - clever alignment of workload with available cores can improve performance significantly. k8s is adding this capability to the CPUManager, and MicroShift should allow and support to utilize this.
Scenarios
- As a user, I must be able to activate the prefer-align-cpus-by-uncorecache policy via MicroShift configuration.
- As a user, I must receive the same SLA for prefer-align-cpus-by-uncorecache as it it is in OCP (TechPreview, GA).
Acceptance Criteria
- CI - MUST be running successfully with tests automated
Dependencies (internal and external)
- USHIFT-6079: Explorative work and design proposal.
Previous Work (Optional):
Upstream KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4800-cpumanager-split-uncorecache/README.md#summary
Promotion PR to Beta in k8s 1.34: https://github.com/kubernetes/enhancements/pull/5390
OCP Tech Preview support statement: https://docs.google.com/presentation/d/1o_vniu1wT2C34I0q8RfGUx15YnRYGfi4cSk7k0dnOK8/edit?slide=id.g3209373ca5a_2_0#slide=id.g3209373ca5a_2_0
Done Checklist
- CI - CI is running, tests are automated and merged.
- DEV - Downstream build attached to advisory: <link to errata, TBD>
- DOC - Downstream documentation merged: <link to meaningful PR, TBD>
- depends on
-
USHIFT-6079 Improve FeatureGate handling in MicroShift
-
- In Progress
-