-
Notifications
You must be signed in to change notification settings - Fork 7k
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
The network is too slow for download helm. #7028
Comments
Thanks for your feedback! A bit of background context on the move to get.helm.sh can be found here: https://helm.sh/blog/get-helm-sh/ Our previous infrastructure was hosted on Google Cloud Storage, which is completely blocked in China. One of the main goals with the migration was availability in China. Azure CDN can serve content to China users with point-of-presence (POP) locations near China. I believe the POP originates from Singapore, if I'm not mistaken. If there's a large enough demand, we can consider hosting them from Azure CDN China which has POPs inside China. |
I think the download speed in China is totally unbearable. Most people in China are using some mirrors like https://mirror.azure.cn/kubernetes/helm/, but those mirrors are often outdated and unsafe. I am sure there's a large enough demand but those people with a poor network condition may not know how to share their voice. I'm thanksful the helm community had done something for China users. But to be honest, something happened is not something worked. The problem is not resolved for now. |
I find the mirror of china , it's huawei! so greate!
|
Had the same issue that the download speed is to slow using https://get.helm.sh in China and often the download just collapses. |
The problem is that most CDN services serve content globally except for China. To have an "official" CDN, we would need another CDN service specifically within China such as Azure CDN China: https://docs.microsoft.com/en-us/azure/cdn/cdn-china-delivery For the time being, I would recommend checking and verifying the PGP signatures of any release assets. That way you can ensure that the release assets have not been tampered with. Every release's PGP signatures are attached to the official release page. You can fetch them from there, then you can verify the signature against the release tarball fetched from Huawei's mirror. If the verification succeeds, then you know it has not been tampered with. For example: https://github.com/helm/helm/releases/tag/v3.5.4
Hope that helps. |
I’ll pose the same question I asked in another ticket: What CDN services are available within China? Which ones work best, and why? |
Re-opening for further discussion/visibility. |
Appart from the slowness of the download, the IP behind https://get.helm.sh ( More precisely, it was identified as a "Command and Control" server for ransomware attack using Emotet. Can't you simply add github release assets and keep https://get.helm.sh in current CDN too? |
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
why helm is at https://get.helm.sh? in china ,it's hard to download,The network is too slow。
and i can't get the latest version of helm from github
can you put it at github,then i can awlays use a automatic command download the latest version and put it in my local network.
The text was updated successfully, but these errors were encountered: