-
Notifications
You must be signed in to change notification settings - Fork 365
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
v0.10.5 is failing due to stable repo move #649
Comments
Hi @dfry, as of our v2.0.0 provider release, we are no longer supporting Helm 2. It is explained in our upgrade guide |
I'm seeing this error using helm v3.3.3 also. |
I'm seeing this with helm version v3.4.4 |
Looks like the old URL is hard-coded into the 0.10.5 version of the provider here: https://github.com/hashicorp/terraform-provider-helm/blob/v0.10.5/helm/provider.go#L452 Based on their blog post it sounds like the stable repo is deprecated and will eventually be garbage collected, but they're going to keep what's there around as an archive. I'm going to cut a hotfix release to change the URL in the old provider so folks stuck maintaining legacy aren't left hanging, but after this please upgrade to the latest provider version! You'll have to fork this repo to keep supporting this if you don't. |
@aareet For me, the error comes before any repos exist. I run terraform in a docker container, so its fresh everytime. There are no repos to update with |
I'm now checking on upgrading to Helm3 right now, but as mentioned the url is hardcoded in 0.10.x provider version, anyhow if this can help somehow I had a local cache of that file from some days ago. |
Provider 0.10.5 |
I am cutting a release for v0.10.6 now @savvys. |
Thanks a lot @jrhouston |
Thank you so much @jrhouston. I have one question, I noticed that your PR for 0.10.6 was already merged but now when I try to use it from Terraform seems that it's not found yet, is there some review process or similar before it's publicly available? |
@sergio-dreamcode you'll need to wait until it appears here: https://releases.hashicorp.com/terraform-provider-helm/0.10.6/ (which it has now) |
@sergio-dreamcode There is a release pipeline that happens after the merge that builds all the appropriate binaries and uploads them to a CDN. I was just able to pull it down so it should be available now – sometimes it can take a few minutes to roll out so try again in a few. |
Thanks for the quick turnaround @jrhouston , the provider is working as expected again. We have been working to convert to helm3 but we have a very large number helm deploys to regression test on helm3 and this repo becoming unavailable caught us at the worst time (during a prod release, of course). Thanks again for the speedy resolution. |
No problem @dfry thanks for contributing. Good luck with your upgrades! 🤠🔧 |
The old repo url does not resolve causing build failures. Changing default value hashicorp/terraform-provider-helm#649
This is a fix for a helm error that started today when building apps: ``` Initializing helm... Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Failed to fetch https://kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden ``` As seen: https://concourse.services.alpha.mojanalytics.xyz/teams/main/pipelines/segmentation-tool/jobs/deploy/builds/20 This was due to today Google getting rid of the 'stable repo' that Helm v2 uses. See: hashicorp/terraform-provider-helm#649 (It was deprecated in Oct). By setting a different, valid stable_repo, helm works.
Change the default value of stable_repo_url since the old one is invalid now. Changes in the original repo have not been made yet hashicorp/terraform-provider-helm#649
Since helm v2.17.0 the stable chart repositories were moved to a new URL, and since a few weeks ago the old repository is no longer available which is causing anyone using helm v2 with kubergrunt to fail. Ideally everybody should be moving to helm v3, but this PR changes the URL to the new repository as a hotfix for those still using helm v2. For context See: - https://github.com/helm/helm/releases/tag/v2.17.0 - hashicorp/terraform-provider-helm#649
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Terraform, Provider, Kubernetes and Helm Versions
Affected Resource(s)
Error: error initializing local helm home: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Failed to fetch https://kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden
Community Note
The text was updated successfully, but these errors were encountered: