-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
R&D Manifest lists support
-
False
-
False
-
Done
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
Epic Goal
- Add support of manifest lists (Docker schema 2 and OCI images).
Why is this important?
- Customers may want to push manifest list into the integrated registry or to leverage pull-through for manifest lists.
- Today OpenShift imports a manifest for the current architecture when it is requested to import a manifest list. As the manifest itself is not imported, clients that rely on digests cannot use this image.
Scenarios
- Mirroring manifest lists into the integrated registry (either via pushing them or via importing them).
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>