-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Allow /dev/fuse by default in CRI-O
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1009 - Enable /dev/fuse in unprivileged containers within OpenShift
-
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- Give users the ability to mount /dev/fuse into a pod by default with the `io.kubernetes.cri-o.Devices` annotation
Why is this important?
- It's the first step in a series of steps that allows users to run unprivileged containers within containers
- It also gives access to faster builds within containers
Scenarios
- as a developer on openshift, I would like to run builds within containers in a performant way
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- is depended on by
-
OCPSTRAT-1009 Enable /dev/fuse in unprivileged containers within OpenShift
-
- Closed
-
- links to