-
Notifications
You must be signed in to change notification settings - Fork 283
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
Chart Repository DNS / Down #1350
Comments
The whole banzaicloud.com domain is down (missing dns), I'm pretty sure we've seen this issue before so probably just a matter of waiting for it to be resolved although rather annoying as we use flux to install helm charts and we are now getting constant failure alerts similar to @levirosal {sarah@saz-omen}$ host kubernetes-charts.banzaicloud.com
Host kubernetes-charts.banzaicloud.com not found: 2(SERVFAIL)
{sarah@saz-omen}$ host banzaicloud.com
Host banzaicloud.com not found: 2(SERVFAIL) |
Maybe host the Helm charts in an OCI repository here on GitHub instead? |
We have same troubles too. |
Same issue with us |
Any hope to get this one resolved, it has been already 4-5 days. |
Same issue here for several days now. Anyone know of a mirror? I see this issue came up November of last year too but was closed within 24 hours. |
Same issue with us |
1 similar comment
Same issue with us |
Same issue here.
|
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
as a temporary fix - I have setup a backup infrastructure for this (but only the latest versions of the charts are available) REPO_NAME=dharapvj-banzai
#REPO_NAME=banzai-charts
helm repo add $REPO_NAME https://dharapvj.github.io/ex-banzai-charts/
helm repo update $REPO_NAME
helm search repo $REPO_NAME | grep spark Let me know if you face any difficulties by creating issue at https://github.com/dharapvj/ex-banzai-charts/issues |
That DNS entry was a CNAME, I believe, it pointed at: https://banzaicloud-kubernetes-charts.prod.eticloud.io/ Which still seems to be up... No idea how long any of this stuff will stay up, seems like it's become (or becoming) abandonware. |
+1 |
For anyone who came here for the We need to understand that this project is migrated to it's own org. I think this is the updated Chart URL : oci://ghcr.io/bank-vaults/helm-charts/vault-operator also, if you are using image:
repository: ghcr.io/bank-vaults/vault-operator
tag: v1.22.3
bankVaults:
image:
repository: ghcr.io/bank-vaults/bank-vaults
tag: v1.31.2 read this : https://github.com/orgs/bank-vaults/discussions/2118 |
To tackle this issue we have implemented the local chart instead of pulling it from banzai repo by getting the chart from here https://artifacthub.io/packages/helm/banzaicloud-stable/vault-secrets-webhook. I could find the templates for the exact version of the chart i was already running in the cluster from Artifact HUB and downloaded the chart of the same version and installed it in the cluster and it seems to be working fine. |
Seems we're going to have to migrate to a different kafka-operator chart :( |
@Surya-Yara I could not find the template option working. if you can help me pointing out to the 1.13.1 version of Vault. That would be great. |
@gunnykc you need to build a chart locally by downloading the templates from the ArtifactHUB. Keep all the templates in templates folder and create a Chart.yaml file as well and create the chart. If you are looking for the vault operator chart of version 1.13.1 which is this https://artifacthub.io/packages/helm/banzaicloud-stable/vault-operator/1.13.1 and if you are looking for vault-secret-webhook chart of 1.13.1 that is here https://artifacthub.io/packages/helm/banzaicloud-stable/vault-secrets-webhook/1.13.1 |
It's been working again since this morning ! |
To me it appears down again :'( |
+1 |
We're experiencing the same issue:
|
you should migrate to |
+1 |
i still see the issue ... any temp fix here ? |
Seem that dnssec in this domain has been activated
Maybe we need to wait a dns propagation |
Is there a new update here? |
I can no longer resolve
kubernetes-charts.banzaicloud.com
has this been moved ?The text was updated successfully, but these errors were encountered: