-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Sparse Manifest
-
False
-
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1808 - oc-mirror v2: Multi-arch filtering via Sparse Manifests
-
OCPSTRAT-1808oc-mirror v2: Multi-arch filtering via Sparse Manifests
-
100% To Do, 0% In Progress, 0% Done
-
---
-
---
Possible Solution:
- Solution 1: copy the manifest list as it is with its signature (cosign tag-based).
Requirement 1: To test this solution it is necessary a registry which supports sparse manifest (does not verify if all the images on the manifest list are present). Also with this solution the customer should use a supported registry.
Requirement 2: OCPSTRAT-1869 / CLID-289 needs to be done
Open Questions:
- Level of the signature
Question 1: Is the signature in the higher level (manifest list) or is it on the manifest level (image level) ?
Dependencies
- CRI-O: should work already (need QE to verify): OCPNODE-2713
- `containers/image` library: ~Jan/Feb 2025: RUN-2377
- Quay: ~Jun 2025: PROJQUAY-3114
- depends on
-
CLID-289 As a user I would like to mirror the signatures of the container images
- New
-
OCPSTRAT-1869 [Phase 1: Cosign tag-based discovery] oc-mirror v2: Discover and mirror SigStore-style attachments
- New