-
Notifications
You must be signed in to change notification settings - Fork 835
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
Helm failing to fetch https://kubernetes-charts.storage.googleapis.com/ resulting in failing tests #2808
Comments
Solved this problem by removing the registry config file and cached repository indexes. type |
This workaround does not work for me. I am having the same issue, but with https://svc-catalog-charts.storage.googleapis.com: (base) [opc@bastion ~]$ helm repo add svc-cat https://svc-catalog-charts.storage.googleapis.com This worked in the past, wondering what has changed... |
@doschkinow google retired that URL and threw a 401 instead of a 301 for some reason. You want to use https://charts.helm.sh now. something like |
@jlamb1 Thanks! But this does not help: [opc@frankfurt ~]$ helm repo list I need the svc-cat charts from https://svc-catalog-charts.storage.googleapis.com, they are not in the stable helm repo. |
resolved: a workaround for me was to get the service catalog charts not from google but directly from github: helm repo add svc-cat https://kubernetes-sigs.github.io/service-catalog Still would be interesting to know why https://svc-catalog-charts.storage.googleapis.com does not work ... |
|
Directly using |
The old one was retired: SeldonIO/seldon-core#2808 (comment)
https://helm.sh/blog/new-location-stable-incubator-charts/
option |
|
Currently helm is failing when fetching
https://kubernetes-charts.storage.googleapis.com/
.The logs appear as follows:
This issue does seem to appear quite a lot online and seems it may not be necessary so the fix may just require removing that from the helm install (eg https://stackoverflow.com/questions/61954440/how-to-resolve-https-kubernetes-charts-storage-googleapis-com-is-not-a-valid)
The text was updated successfully, but these errors were encountered: