-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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.
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
Harbor as a pull cache and private registry #6863
Comments
@clouderati I'd be happy to help any way I can with this feature, especially testing. I don't have any substantial Go experience, but I have a couple high-level thoughts about how this could be implemented based on your current deployment model(unless you already have an implementation in mind). |
Testing is super helpful! I'll ping you when the feature gets closer to release and perhaps you can give it a whirl and share your 2¢. 😄 Thanks! |
Awesome! Looking forward to hearing more and trying it out once it's ready 😄 |
I really like this idea! any progress? |
duplicate with #6894 ? |
I'm closing this please refer to 8082 above |
We're looking to use Harbor as a private registry and would like it to also serve as a pull-through cache for the official Docker registry.
This feature is desirable for our use case because our Kubernetes cluster nodes have limited public ingress/egress points, and we'd like to be able to cache official Docker images locally to reduce the load on our public network devices, while still maintaining the ability to push our custom images to the same Harbor instance from our CI environment.
The text was updated successfully, but these errors were encountered: