-
Notifications
You must be signed in to change notification settings - Fork 72
HELM proxy The proxy does not use the original absolute address #8
Comments
See PR #4. I'm guessing its the same issue. |
Hmmm, this is gonna be tricky actually. Being they use a different URL for the charts than the actual repo, we'd need to make outbound requests to whatever the URL indicates. I'll see if I can noodle on this in a bit, but other PRs, etc... are welcome! The url itself needs to be set to relative versus absolute so that requests are made through Nexus Repo (otherwise what's the point of using it, hah), but this is kinda interesting in that they are maintaining two different URLs (one for the repo, one for their charts). |
There are two different addresses for a helm repo, there is a way to handle it,
Fortunately, the situation is now the first one in chart.gitlab.io, then the solution is to set https://gitlab-charts.s3.amazonaws.com to the remote proxy address. like this |
@loverto you are correct, you can totally do that as long as the index.yaml and the charts are accessible via that URL. It might be worth reaching out to the maintainers of that repo and asking them why they maintain two separate URLs, maybe they can merge them. I can totally understand wanting to host your charts on S3 or something akin, but if the index is also there it just begs the question of why you'd have two different URLs in general. |
I have also encountered this issue with a few helm repos. (e.g. https://helm.elastic.co/ or https://oteemo.github.io/charts) In elastic's case they serve the .tgz files on the same domain, but under different subpaths. For example the .tgz file for apm-server is at: Lines 113 to 119 in b7afdc5
If more and more repos deprecate the stable repo and take the same route to host their files, proxying will possibly be useless. |
The issue in https://issues.sonatype.org/browse/NEXUS-20929 was marked as "wont fix", don't know why, hope this can be fixed in the comming releases. |
Related ticket. https://issues.sonatype.org/browse/NEXUS-24682 |
Thanks for creating an issue! Please fill out this form so we can be
sure to have all the information we need, and to minimize back and forth.
I try to use one helm repo proxy ( to https://charts.gitlab.io ) but I have :
helm repo add nexusrepo http://nexus/repository/helm-stable-proxy/
helm fetch nexusrepo/mongodb
Error: Failed to fetch http://10.100.100.11/repository/helm-gitlab-charts/auto-deploy-app-0.2.4.tgz : 404 Not Found
Server-side log open DEBUG see the following log
What feature or behavior is this required for?
How could we solve this issue? (Not knowing is okay!)
Anything else?
There is a problem here, adding that the chart is not the official address, that is to say, the downloaded address is not the same domain name as the chart, there will be problems, for example, https://charts.gitlab.io
His index.yaml format is like this
The text was updated successfully, but these errors were encountered: