Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Error: looks like "https://svc-catalog-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: failed to fetch https://svc-catalog-charts.storage.googleapis.com/index.yaml : 403 Forbidden #2869

Closed
fanchenxu-ship opened this issue Dec 23, 2020 · 4 comments

Comments

@fanchenxu-ship
Copy link

fanchenxu-ship commented Dec 23, 2020

Bug Report

What happened:
when i run "helm repo add svc-cat https://svc-catalog-charts.storage.googleapis.com" it failed.
Error message:
Error: looks like "https://svc-catalog-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: failed to fetch https://svc-catalog-charts.storage.googleapis.com/index.yaml : 403 Forbidden
Environment:

  • helm version: v3.4.2
@jiayihu
Copy link
Contributor

jiayihu commented Dec 30, 2020

What worked from me was downloading the chart from https://github.com/kubernetes-sigs/service-catalog/tree/master/charts/catalog and installing it locally.
I also changed the image to image: quay.io/kubernetes-service-catalog/service-catalog-arm64:v0.3.1 since i'm using ARM64/aarch64

@achrinza
Copy link

achrinza commented Jan 3, 2021

This should be updated command:

helm repo add service-catalog https://kubernetes-sigs.github.io/service-catalog

AFAIK, #2841 and the Google Group announcement discusses this shift.

Though the docs should probably be updated too to reflect this change.

@streamnsight streamnsight mentioned this issue Jan 4, 2021
10 tasks
@kjaksik
Copy link
Contributor

kjaksik commented Jan 5, 2021

It also happens during CI pipelines. Helm in version 2.16.7 had the repo hard coded and helm init tried to reach this repo. Should be fixed in #2873

@jhvhs
Copy link
Contributor

jhvhs commented Jan 10, 2021

Fixed the documentation in #2875

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants