Open ramarnat opened 2 years ago
It appears as though you can perform a login to an insecure registry, but you cannot pull from an insecure registry.
If I do not provide credentials, the error message is as follows:
create failed: failed to install release: failed to login to registry: Get "http://registry:5000/v2/": no basic auth credentials
When credentials are provided, it appears to perform the login without issue, but errors on the pull:
failed to install release: failed to pull chart: failed to do request: Head "https://registry:5000/v2/helm-charts/mychart/manifests/1.0.0": http: server gave HTTP response to HTTPS client
I do not know go, but it seems as though, the InsecureSkipTLSverify
bool is not being passed to the Pull client.
Edit: Looks like this may not even be possible until this is merged? https://github.com/helm/helm/pull/10408
Looks like this MR adds the missing functionality: https://github.com/helm/helm/pull/11599
Related to #202
I'm hoping this is either possible or closer to possible now that #202 has been resolved. If someone wants to try this scenario out and take it to the finish line if needed, that could be a welcome contribution 🙇
This probably does solve it, but I am not working with the original product that required having this issue resolved.
What happened?
I have setup a local registry based on the instructions here - https://kind.sigs.k8s.io/docs/user/local-registry/
When setting the helm chart properties, using oci (the registry was loaded with the oci pkg):
I have tried a bunch of different options, but none of them work. If we use a named
registry
the provider tries to use https:// , and produces this error:In kind the configuration for skipping tls is also set:
How can we reproduce it?
What environment did it happen in?
Crossplane version: