Closed haarchri closed 3 months ago
okay found it
removed the following entry from: /Users/haarchri/Library/Preferences/helm/repositories.yaml
- caFile: ""
certFile: ""
insecure_skip_tls_verify: false
keyFile: ""
name: abc/abc/xx
pass_credentials_all: false
password: ""
url: us-west1-docker.pkg.dev
username: ""
Hi @haarchri, Did this entry appear due to Helmper, or was it already present in the config?
This was added by helmper
I see this is related to #40 as Helmper has added the entry to the repositories.yaml file, which does not work when using helm repo add
with the Helm SDK. To avoid this causing problems, i will add a simple check to confirm the repo has http/https protocol before adding it to the repositories.yaml file
These commands does not work:
helm repo add test prometheus-community.github.io/helm-charts/
helm repo add test oci://prometheus-community.github.io/helm-charts/
helm repo add test tcp://prometheus-community.github.io/helm-charts/
These commands works
helm repo add test https://prometheus-community.github.io/helm-charts/
helm repo add test http://prometheus-community.github.io/helm-charts/
It looks like helm repositories does not currently support OCI, only the following commands has support for OCI:
https://helm.sh/docs/topics/registries/#commands-for-working-with-registries
I will have to consider how Helmper is supposed to work when the source is OCI, for now i guess Helmper only works when targeting OCI registries
after a few tries for gke registry logins - i get only the following issue: