-
Feature
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
False
-
Not Set
-
No
-
Not Set
-
Not Set
-
Not Set
-
Undefined
Feature Background & Overview
- Some customers require kernel drivers that aren't included in the RHEL kernel ("out of box" or OOB drivers). The Special Resource Operator (SRO) can handle most of these cases as a day 2 operation.
- This feature is intended to cover drivers that are required for day 1 node installation and early boot ("early boot drivers" for now until we think of something snappier). Typically this is a network or storage driver.
- RHEL has a mechanism to handle this. Red Hat distributes supported driver updates for RHEL outside of the standard kernel that can be used for installation and early boot. For more information on the RHEL Driver Update Program see: https://docs.google.com/presentation/d/1BnXzcS1VnSWxGOYUCLpKvulmPggT4i1bvWpDLEYq5CQ/edit#
- Currently RHCOS has no way to consume third party or Red Hat supported OOB drivers in early boot
Goals
- OpenShift can be installed on hardware requiring out-of-box early boot drivers in the initrd
- Provide a method for life cycle management of add-on drivers
- Cluster administrators can confidently manage platform updates without worrying that their OOB kernel drivers will break
Requirements
| Requirement | Notes | isMvp? |
|---|---|---|
| Customer can load OOT driver required for installation and day 2 initramfs stage. | 3rd party drivers and RHEL DUP drivers | Yes |
| OOT driver life cycle can be managed in the event of kABI changes | 3rd party drivers and RHEL DUP drivers | Yes |
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. | YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. | YES |
Out of Scope
- …
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
- Does this feature have doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content Strategy.
- What concepts do customers need to understand to be successful in [action]?
- How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
- What is the doc impact (New Content, Updates to existing content, or Release Note)?