-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
None
-
0% To Do, 100% In Progress, 0% Done
-
False
-
-
False
-
XS
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Provide a controlled and supported way to use FeatureGates (from k8s and OpenShift)
Goals (aka. expected user outcomes)
Users are able to use FeatureGates with MicroShift, while default features gates in Microshift are well aligned with what is inherited from OpenShift.
Requirements (aka. Acceptance Criteria):
- It must be part of the automated rebase of MicroShift to have default feature gates aligned with OpenShift, to avoid issues we had with the Kube 1.33 rebase of misaligned feature gates and previously (see USHIFT-2813) )
- Users must be able to configure / enable feature gates in a controlled and deterministic way. For example the CPUManager prefer-align-cpus-by-uncorecache alpha/beta feature. (see OCPSTRAT-2333)
Questions to Answer (Optional):
- tbd
Out of Scope
- tbd
Background
Also see the Arch Meeting recording on Apr 2nd 2024
Customer Considerations
Documentation Considerations
Procedure to configure feature gates need to be documented in the configuration section.
nteroperability Considerations
none
- blocks
-
OCPSTRAT-2333 Last Level Cache locality for MicroShift
-
- Backlog
-
- clones
-
OCPSTRAT-2333 Last Level Cache locality for MicroShift
-
- Backlog
-
- is blocked by
-
USHIFT-2813 Handle accommodating different conflicting Feature Gate defaults
-
- To Do
-
- is triggered by
-
RFE-7931 AMD Last Level Cache Affinity for MicroShift
-
- Approved
-
- links to