Proposal: Enhanced Proxy-Cache Structure for Harbor

[parisnakitakejser]

When using Harbor, I would like to leverage it as a central proxy in front of all images deployed into my Kubernetes cluster.

Currently, as I understand it, using the proxy-cache feature requires creating a separate registry for each external source (e.g., Docker Hub, Quay, GHCR). This approach quickly becomes cumbersome to manage when multiple proxy caches are needed.

I propose an enhancement to allow creating proxy-cache registries within a single Harbor registry, using a structure such as:

proxy-cache/{source}

For example:

• proxy-cache/docker-hub
• proxy-cache/quay
• proxy-cache/ghcr

This structure would:

• Simplify management and maintenance of proxy images.
• Allow consistent and predictable naming conventions.
• Make cleanup policies easier to define and apply.
• Provide more flexible and generic access control for proxy-cache usage.

This improvement would make Harbor more powerful as a unified image gateway while maintaining clarity and scalability in multi-source environments.