Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Epic: Proxy Cache user stories #11658

Closed
xaleeks opened this issue Apr 18, 2020 · 4 comments
Closed

Epic: Proxy Cache user stories #11658

xaleeks opened this issue Apr 18, 2020 · 4 comments
Labels
area/proxy-cache doc-impact Engineering issues that will require a change in user docs Epic target/2.1.0

Comments

@xaleeks
Copy link
Contributor

xaleeks commented Apr 18, 2020 •
edited
Loading

This is an epic tracking all user stories for Harbor functioning as proxy cache for upstream registries
This was referenced May 9, 2020
Closed
Closed
Closed
Closed
Closed
Closed
Closed
This was referenced May 29, 2020
Closed
Closed
@mvisonneau
Copy link

mvisonneau commented Jul 15, 2020 •
edited
Loading

I am so excited to see this feature being 🚀 , thanks guys! 🙇

@xaleeks
Copy link
Contributor Author

xaleeks commented Aug 6, 2020

@a-mccarthy fyi

@xaleeks xaleeks added the doc-impact Engineering issues that will require a change in user docs label Aug 6, 2020
@xaleeks xaleeks mentioned this issue Aug 26, 2020
Open
@Morriz
Copy link

Morriz commented Jan 3, 2022

@reasonerjt why was this closed? I can't find any evidence that it is now possible to do automatic image scanning of proxied images? Or is that tracked somewhere else now?

@candoom
Copy link

candoom commented Jan 18, 2022

Is this feature still planned or completely discarded? I would be very interested in it as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/proxy-cache doc-impact Engineering issues that will require a change in user docs Epic target/2.1.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@candoom @Morriz @mvisonneau @reasonerjt @xaleeks