-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
4.17 User Namespace Work
-
Strategic Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-207 - TP in 4.17 : Support User Namespaces in pods
-
OCPSTRAT-207TP in 4.17 : Support User Namespaces in pods
-
0% To Do, 0% In Progress, 100% Done
-
L
Epic Goal
- Allow users of Openshift to enable user namespaces in a supportable way. For 4.17, this may be a TechPreview or it may be straight to GA.
- As a side effect of this, have a supportable unprivileged podman in Openshift configuration for users to develop in, especially in Openshift DevSpaces
Why is this important?
- User namespaces both enhance the security posture of clusters, as well as open up capabilities that containers couldn't previously take advantage of
- Capabilities like podman in openshift
Scenarios
- ...
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>