We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
While adding a helm repo the url is https://kubernetes-charts.banzaicloud.com cannot be reached.
Steps to reproduce the issue:
helm repo add benzaicloud-stable https://kubernetes-charts.banzaicloud.com
Error: looks like "https://kubernetes-charts.banzaicloud.com" is not a valid chart repository or cannot be reached: Get "https://kubernetes-charts.banzaicloud.com/index.yaml": dial tcp: lookup kubernetes-charts.banzaicloud.com on 127.0.0.53:53: no such host
Expected behavior
Repo should be added correctly Screenshots
Additional context
The text was updated successfully, but these errors were encountered:
Same :( Is banzaicloud dead? Did Cisco finally kill it?
Sorry, something went wrong.
It looks like Banzai Cloud was quietly killed by Cisco in late 2024.
The Helm chart repo hasn't been accessible since 3 October 2024, alongside their main sites (https://banzaicloud.com, https://banzai.cloud, https://banzaicloud.io).
See also: publicsuffix/list#2215
No word from any past or present employees or other involved persons. I don't think it's coming back, so you should plan accordingly.
No branches or pull requests
Describe the bug
While adding a helm repo the url is https://kubernetes-charts.banzaicloud.com cannot be reached.
Steps to reproduce the issue:
helm repo add benzaicloud-stable https://kubernetes-charts.banzaicloud.com
Error: looks like "https://kubernetes-charts.banzaicloud.com" is not a valid chart repository or cannot be reached: Get "https://kubernetes-charts.banzaicloud.com/index.yaml": dial tcp: lookup kubernetes-charts.banzaicloud.com on 127.0.0.53:53: no such host
Expected behavior
Repo should be added correctly
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: