-
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
Helm repository proxy #6526
Comments
Thanks for reaching us and sharing your scenario. So far, Harbor can not support mirror/proxy to upstream chart repos, but we're doing some work to improve the replication service to support covering helm charts. In future, maybe you can create replication rule to let harbor automatically pull images from the specified upstream chart repos you specified. Please stay tuned. |
I will. |
You can take care of this issue. We can consider if we can leverage the replication to support chart repo mirror in the future release. |
Any update on the future release to support this? |
@mumrau I would encourage you to share your usage and track progress here #8082 and I'd like to close this one so we consolidate all the requirements down to a single place. Harbor 2.0 supports OCI fully which means helm charts can now reside in the docker registry alongside container images as opposed to hosting them separately in chartmuseum. This means we will probably deprecate chartmuseum at some point in the future and so any proxy cache mechanism for helm charts should be explored as part of a larger story to have this ability for all OCI artifacts, hence the ticket I linked. |
Is your feature request related to a problem? Please describe.
I would like to manage in my company helm charts as we proceed with everything else that looks like or is an artifact. In that sense, we would like to have the possibility of configuring a proxy repository for helm/stable.
Describe the solution you'd like
I would like the possibility to configure helm repository mirror/proxy solution in harbor.
Describe the main design/architecture of your solution
To be determined. Depends on chartmuseum I believe. I know the sonatype helm "solution" (which is extremely unstable) has this kind of behavior.
Describe the development plan you've considered
I don't have any idea yet, as I'm just approaching harbor since a few days. I suspect the implementation isn't that hard but might be tricky. Somebody else can probably answer this part better.
Additional context
Empty.
The text was updated successfully, but these errors were encountered: