aws / aws/containers-roadmap

[ECR] [request]: Pull through cache support for Harbor Container Registry

Open
#2,622 0 comments 17 reactions 0 assignees View on GitHub
ECR Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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**
We would like to use pull through cache with Harbor container registries with credentials.

**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?**
We would like to use pull through cache with Harbor container registries.

**Are you currently working around this issue?**
We are currently unable to use pull through cache with Harbor registries as it is not yet supported as an upstream source registry.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are mentioned in the issue. Start by identifying where ECR pull-through cache upstream registries are defined and how credentials are handled; done means Harbor container registries are supported as authenticated upstream sources.

Written by the indexing model from the issue text.

Assessment

Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.