You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Tags are not deterministic. They are mutable and volatile. There is no guarantee that in time same content will be pointing to tag e.g. 'latest'.
Describe the solution you'd like
To solve the issue of reproducibility one could be using digests, as they are content addressable and instead mirror content by digest.
Container registry does not provide API endpoint that would list all manifest digests present within the repo as it is possible with tags/list endpoint, hence we need to add digests_list field to pulp-container-remote that will enable user to provide a list of manifest digest to mirror from the remote registry.
In addition to this we could add an extra registry endpoint that would be accessible only between pulp instances. Instead of providing really long list of digests(unless a specific list is desired) one could just hit this endpoint /v2/<name>/manifests/list and all manifests will be discovered by digest. That could be an extra option on the remote that would in addition to regular tag dicovery also try to access manifests/list endpoint and fetch the rest of un-tagged manifests.
This is about facilitating the sync between multiple Pulp instances to ensure that clients are downloading manifests by digests. We want to provide reproducible environment for our users. The reference by tags is not always "reliable" -- content/manifest behind the tag can change. The reference by digest will never change. The idea is to provide/host/mirror the list of digests.
Is your feature request related to a problem? Please describe.
Tags are not deterministic. They are mutable and volatile. There is no guarantee that in time same content will be pointing to tag e.g. 'latest'.
Describe the solution you'd like
To solve the issue of reproducibility one could be using digests, as they are content addressable and instead mirror content by digest.
Container registry does not provide API endpoint that would list all manifest digests present within the repo as it is possible with
tags/list
endpoint, hence we need to adddigests_list
field to pulp-container-remote that will enable user to provide a list of manifest digest to mirror from the remote registry.Describe alternatives you've considered
None
Additional context
https://issues.redhat.com/browse/SAT-24032
https://issues.redhat.com/browse/OSPRH-1338
The text was updated successfully, but these errors were encountered: