Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
Currently, AWS ECR supports authenticated pull through cache for registry.gitlab.com, however it does not support self-hosted Gitlab instances. For customers who self-host Gitlab, using ECR as a pull through cache is impossible.
Which service(s) is this request for?
ECR
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
For security and compliance reasons, we prefer to give clients access to our ECR registry, rather than our self-hosted Gitlab registry.
Are you currently working around this issue?
Currently, we have to maintain custom automation to push new images into ECR and to create ECR repositories. We would like to have the features of an ECR pull through cache connected to a self-hosted Gitlab instance.
Additional context
In general, I don't understand why AWS restricts pull-through cache to specific hosts. As far as I can tell, as long as a registry is conforming to the oci distribution spec, AWS should have a standard interface for authenticating and pulling images from a vast array of registries.