-
Notifications
You must be signed in to change notification settings - Fork 44
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
Error: failed to download oci://localhost:5001/test-chart
with Kind and local registry
#168
Comments
In addition to the
Error on the
|
I expect this has to do with the details of local kind registry rather than a bug in helm/oci. From https://kind.sigs.k8s.io/docs/user/local-registry/#using-the-registry
Have you tried using If that doesn't work - For our local/kind e2e testing we spin up a git server as a service in the cluster. We don't have any local/kind e2e testing for oci/helm yet, but the way I would probably go about that is to spin up the registry as a service in the cluster as well. |
Hi @sdowell, to be honest I think I would like to see what could be seen in the code of both paths When I'm looking at this https://github.com/stefanprodan/flux-local-dev, it seems that they are able to deploy their OCI artifacts with the exact same setup as mine. I'm trying to see if there is any differences or something I'm missing. For exampe, I see that in their And I think this setup could be a good win for the CI/e2e tests of CS with Helm/OCI too, as soon as we get this working? Back to your suggestion:
What do you mean? In the name of the image when doing |
Our kind tests run in parallel on multiple clusters so for our e2e testing use case we would probably want to isolate the registry for each cluster anyways. From kind's documentation it sounds like |
Gotcha, good catch, I will try that soon and will report back here, thanks @sdowell.
Same for Helm. |
Hey @sdowell, following up on this, I just did some tests with For
And with
For
|
It appears this has to do with the I don't think our API currently supports toggling that flag and it's not currently planned to add support for that in the API. I expect it's a similar scenario for helm but it's just returning a generic error. |
Hi @mathieu-benoit, I will look into this for helm support and let you know. Thanks @sdowell for helping do the initial analysis. |
I confirmed that the |
Hi @mathieu-benoit, I am able to reproduce the Helm failure. When I debug it, I see the error message |
Thanks @nan-yu for tracking the issue internally for OCI. Thanks @xinnywinne for diagnosing the issue with Helm. The link you shared is about the |
helm pull/push/template work with |
I'm trying to sync an Helm chart with Config Sync installed in Kind with a local registry, but I'm getting this error on my
RootSync
:Here is my setup to reproduce:
JFYI, if I don't use the local registry setup, but instead use a public Helm chart in GHCR, it's working successfully:
Also, I confirm that this
docker
flow is working successfully with this setup too:Not sure if the error is coming from the Kind setup or from Config Sync, so logging this here.
CC: @nan-yu @xinnywinne
The text was updated successfully, but these errors were encountered: