-
Story
-
Resolution: Unresolved
-
Critical
-
None
-
5
-
False
-
None
-
False
-
-
-
Pipelines Sprint TekShift 14, Pipelines Sprint TekShift 15, Pipelines Sprint TekShift 16, Pipelines Sprint Tekshift 17
Story (Required)
slack thread : https://redhat-internal.slack.com/archives/CG5GV6CJD/p1721763098206709
Openshift shipps user namespace as GA in 4.17 which is in October 2024 so lets complete this task by 1.17 OSP
https://issues.redhat.com/browse/OCPSTRAT-207
Background (Required)
<Describes the context or background related to this story>
Out of scope
<Defines what is not included in this story>
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met
- account is impacted by
-
SRVKP-6209 Understand about how User Namespaces works for OpenShift
- Closed
- is cloned by
-
RHDEVDOCS-6240 [DOC] Support User Namespaces for buildah task shipped by ecosystem
- Open
- is documented by
-
RHDEVDOCS-6240 [DOC] Support User Namespaces for buildah task shipped by ecosystem
- Open