Details
-
Story
-
Resolution: Done
-
Critical
-
None
-
False
-
None
-
False
-
OCPBU-185 - Initial Manifest list support for multi-architecture environments
-
Sprint 228, Sprint 229, Sprint 230, Sprint 231
Description
ACCEPTANCE CRITERIA
- Pushing a manifest list to the image registry should result in an image stream created for the manifest list
- Image objects should be created for the manifest list, as well as all of its sub-manifests
- The Image object for the manifest list should contain references to all of its sub-manifests under the dockerImageManifests field
- Pulling a sub-manifest of a manifest list by digest should work when the user has access to the image stream
Notes:
- When a manifest is pushed by sha an Image object should be created
- You can use `skopeo copy` with the `--all` flag to push a manifest list and all its sub-manifests to the registry
- Authorization needs to work the same they do for images created via imagestreamimport
Attachments
Issue Links
- is blocked by
-
IR-262 As an OpenShift user I want my sub-manifests to not be pruned unless the manifest list is deleted (`oc adm prune images`)
-
- Closed
-
- relates to
-
IR-271 As an image registry user I want to push a manifest list by tag so that I can use its sub manifests in a multi-arch cluster
-
- Closed
-
- links to
(1 links to)
1.
|
QE Tracker - IR-270 |
|
Closed | |
xiujuan wang |