Open devantler opened 5 months ago
I am also seeing this with the hosted version:
helm pull oci://chartproxy.container-registry.com/charts.jetstack.io/cert-manager --version v1.11.2
Error: chartproxy.container-registry.com/charts.jetstack.io/cert-manager:v1.11.2: not found
helm pull oci://chartproxy.container-registry.com/zotregistry.dev/helm-charts/zot --version 0.1.60
Pulled: chartproxy.container-registry.com/zotregistry.dev/helm-charts/zot:0.1.60
Digest: sha256:062bacd2dfd2e738ad96f19a87cae8e2589f547952d7599ef59fdd340a6ec89b
Might be an issue with the way they are hosting the jetstack helm repo, although with the url in the logs I am able to just download it by navigating to that url.
If you remove the --version "v" it will work, it looks like the v is appended and removed across a few locations. I am not entirely sure but the Manifest Map doesn't have the v in it, so when it looks up with the target it fails. Somewhere the v needs to be persisted in the version or it needs to just be removed as it is already being dropped in one location.
helm pull oci://chartproxy.container-registry.com/charts.jetstack.io/cert-manager --version v1.11.2
Error: chartproxy.container-registry.com/charts.jetstack.io/cert-manager:v1.11.2: not found
helm pull oci://chartproxy.container-registry.com/charts.jetstack.io/cert-manager --version 1.11.2
Pulled: chartproxy.container-registry.com/charts.jetstack.io/cert-manager:1.11.2
Digest: sha256:9092d6334348d9172684fcd0561c7a798696802f95169b40349b76c02627d81e
https://github.com/container-registry/helm-charts-oci-proxy/blob/main/internal/manifest/manifest.go#L190
I am not entirely sure how m.manifests[repo]
is getting created but that is where the problem is, I am guessing the prepareChart pushes it to the m.manifests in some form but I am not 100% familiar enough to get further than that in this short look.
Hey,
I am scratching my head because the service works well for all our deployments but not for cert-manager. With cert-manager, it seems Chartproxy is unable to convert the Helm Chart to OCI.
These are the logs I am getting:
Below is my HelmRepository and HelmRelease manifests for cert-manager:
And lastly here is my HelmRelease manifest for helm-charts-oci-proxy:
I am using a self-hosted chartproxy, as I owerwrite the
${helm_charts_proxy_url:=chartproxy.container-registry.com}
with the following url:oci://helm-charts-oci-proxy.helm-charts-oci-proxy:9000
, so I am pretty sure that this is not related to caching. I have also checked that the thehttps://charts.jetstack.io/index.yaml
looks as expected. Has anyone experienced this?