Gitlab Proxy Cache

[Heshmatkhah]

Is your feature request related to a problem? Please describe.
Hi,
Why the Proxy Cache is not compatible with GitLab.
Technically, whats the difference between these registries?
Aren't all container registries have same API?

Describe the solution you'd like
Can you please add Proxy Cache support for GitLab?

Thank you

[aureq]

For reference, there was this issue #14234 but it has been automatically closed due to inactivity.

To add, GitLab is a prominent alternative to GitHub. Furthermore, GitLab supports self-hosted container registries so having the ability to override GCR default URL would be most welcome.

[aureq]

It seems possible to add registry.gitlab.com as a Registry in Harbor, however, it's not possible (yet) to create a new project leveraging this remote registry. That remote registry is only available for remote replication.

[stonezdj]

All registries support v2 api, but they have a different implementation on some other API such as authentication, and list artifact API.

[wy65701436]

@Heshmatkhah can you try the workaround the mentioned above? And we have no resource to maintain the Gitlab adapter so far, and any contribution is welcome.

[aureq]

@wy65701436 is there a chance that you could list the various source files on another registry that are required to implement the proxy and adapter please? If that's not too complicated, I could try to submit a PR.

[Heshmatkhah]

Hi

@Heshmatkhah can you try the workaround the mentioned above? And we have no resource to maintain the Gitlab adapter so far, and any contribution is welcome.

The replication rules works as expected for gitlab, but the problem is that I have 1000+ images with many tags, the total registry size on my gitlab instance is 1TB+, I don't need all of theme on my harbor, and I don't have time to write rule for each image to filter tags.
I just need a cache proxy to cache whatever I need.