search

rpardini / docker-registry-proxy

An HTTPS Proxy for Docker providing centralized configuration and caching of any registry (quay.io, DockerHub, k8s.gcr.io)
Apache License 2.0
912 stars 170 forks source link

Harbor support #81

Open roldancer opened 3 years ago

roldancer commented 3 years ago

Hi, First of all ... excellent project !!!!

I would like to know if there is any experience using this projects as a docker proxy for Harbor 2.X ? can anyone provide me any kind of experience , best practices etc.

Many thanks.

brizjin commented 3 years ago

have the same question. how to auth proxy to harbor

hishamanver commented 3 years ago

Hi there, is this harbor cloud or on prem?

With our on prem setup we just create read only robot account which we then configure using the REGISTRIES and AUTH_REGISTRIES vars, i suspect cloud should be similar but I cannot confirm.

The only tweak we required was to add http2 support, which is covered in https://github.com/rpardini/docker-registry-proxy/pull/102

rpardini commented 3 years ago

I'm very interested why one would want to run this in front of Harbor...

flippy1345 commented 1 year ago

To give inside as to why this could be wanted: For us we want to ease the traffic to the registry/harbor by having in kubernetes a per node proxy with caching enabled and having the service set to local traffic to prevent request from unnecessarily going to other nodes.

This Cluster is used for running gitlab pipeline jobs. Those jobs cause daily 2 TB of traffic, which is too much for gitlab ce or minio and probably harbor.

The described setup works as intended, for our docker registry mirror, only harbor auth is not so happy with the proxy.