Open eXist-FraGGer opened 1 week ago
If we have insecure registry (e.g. harbor installed in minikube) - we can not install helm chart "oci://" because it is using https://
The error will be Error: Get "https://.../v2/.../tags/list": http: server gave HTTP response to HTTPS client
Error: Get "https://.../v2/.../tags/list": http: server gave HTTP response to HTTPS client
There is an option in helm --plain-http https://helm.sh/docs/helm/helm_install/
--plain-http
Please do implement
The usage can be:
new k8s.helm.v4.Chart( 'app', { name: 'app', namespace: 'app', chart: 'oci://oci.registry/helm-charts/app', plainHttp: true, // <--- here }, { dependsOn: [appNamespace] } );
Thanks for reporting this issue and a suggested API change. We currently hardcode plainHTTP to be false (ref), so we'll need to expose this as a setting. We'll add this to our backlog to work on.
plainHTTP
false
Hello!
Issue details
If we have insecure registry (e.g. harbor installed in minikube) - we can not install helm chart "oci://" because it is using https://
The error will be
Error: Get "https://.../v2/.../tags/list": http: server gave HTTP response to HTTPS client
There is an option in helm
--plain-http
https://helm.sh/docs/helm/helm_install/Please do implement
Affected area/feature
The usage can be: