-
Epic
-
Resolution: Done
-
Critical
-
None
-
OCP CoreOS Layering - MCO
-
False
-
False
-
Green
-
In Progress
-
OCPSTRAT-143 - Allow admins to add 3rd party and custom content to RHCOS
-
Impediment
-
OCPSTRAT-143Allow admins to add 3rd party and custom content to RHCOS
-
0% To Do, 0% In Progress, 100% Done
-
0
-
0
Minimal goal: minimal design decision (and enhancement) for the interface for the hotfix workflow; describe general goal of user experience
First Enhancement: https://github.com/openshift/enhancements/pull/1032
Stretch: Have a concrete plan that has been approved by team
- Figure out the optimal path for support to troubleshoot with all these additional inputs and layers
- Treat Machine Config as a UX
- Determine impact on support and derive requirements from those experiences (goal would be to reduce the friction that customers have tripped over in the past)
- Decide on format of layers in machine configs
- Get 2 specific use cases/layer candidates that we want to try to support
- Disaster recovery workflows - https://github.com/ostreedev/ostree-rs-ext/issues/121#issuecomment-1005211976 (I didn’t want this to get lost / forgotten in the ether)
- blocks
-
MCO-166 Coreos Derive in Cluster [high level user facing]
- Closed
-
RFE-2136 Allow merging multiple ContainerRuntimeConfig including priorities
- Deferred
-
OCPPLAN-9332 Ability to apply hotfix packages to RHCOS via Layering
- Closed
-
OCPSTRAT-143 Allow admins to add 3rd party and custom content to RHCOS
- Closed
-
OCPSTRAT-161 Allow admins to add add'l RHEL packages to RHCOS
- Closed
- is blocked by
-
MCO-293 Replace machine-os-content with new format base image
- Closed