-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
Notice: the stable Helm charts have been deprecated, new alternatives are required #274
Comments
To be clear, the artifacts have not been deleted, they are hosted indefinitely, sponsored by GitHub. There was a short blip where paths had a typo only for the most recent version. This has been fixed in helm/charts#24424 The chart’s repo is read only, but artifacts are evergreen. Please join the ongoing initiative to move continuing development of chart source code to new repos: https://github.com/helm/charts/issues/21103 |
Thank you for the fix, that's appreciated and takes off some immediate pressure for us. Jenkins has moved here -> https://github.com/jenkinsci/helm-charts Folks, feel free to post links to the above charts and where they have moved to. |
Grafana is available here -> https://github.com/grafana/helm-charts |
@nitishkumar71 and @yankeexe would you be able to help with this? |
Minio is available here -> https://github.com/minio/charts |
@alexellis Do you think, we can use https://github.com/bitnami/charts/tree/master/bitnami for mongo, postgres, sealed secrets(in future) and few other applications in future. As this chart repo will guarantee stability in future. No upstream found for mongo(found for operator) and postgres. |
I've linked to upstream. We should always prefer upstream to Bitnami where available |
@alexellis I could not find any upstream repo for the remaining apps. |
I sent links for Grafana and Jenkins, and you found a link for Minio. Can you start with those? |
should we also upgrade them to new app style? |
Yes go ahead please |
@alexellis would you mind changing the title of this issue? It's still concerning to people who see it but don't read the comments. If you don't mind. thank you! |
@scottrigby if that's the case, can you confirm why we're still seeing this error being reported by users?
|
Hi @alexellis I just answered this at helm/charts#24424 (comment) |
/set title: Notice: the stable Helm charts have been deprecated, new alternatives are required |
Thank you so much @scottrigby - I've updated the title. |
Only need 1 more to go: Mongodb, I think the bitnami chart should be fine there, because Mongodb now uses operators as their offical chart, so it is nowhere close to 1:1 feature parity. |
Thank you @Shikachuu for taking these on. Since this is really about apps for local development, I think that the Bitnami chart would be fine. |
Bitnami images doesn't support ARM arch and they don't have any plan to fix this. |
I was already aware of that. Which chart does that affect that needs to be updated @saggiyogesh ? Do you have an alternative that you prefer? |
@nitishkumar71 the new minio link you added is not available, new issue submitted to fix the repo chart #1012 |
What happened
This is a notice that the stable Helm chart repo has been deprecated and the maintainers have deleted all artifacts for helm charts.
Impact
If you are relying on any charts in the stable repository, you can no longer build new systems or use your applications.
This means you will have to responsibly source an alternative, or fork the stable repository and maintain it yourself. When I say "responsibly source" that means do not just trust a third-party fork of a component you need, it's very easy for someone to deploy malicious code to your cluster that way.
Workarounds
As per https://helm.sh/docs/faq/#i-am-getting-a-warning-about-unable-to-get-an-update-from-the-stable-chart-repository
The stable repo can be used as read-only with previously published versions:
Affected apps
Various Arkade apps used the stable helm chart repo to deploy software to your cluster, where possible third-party projects have already moved to their own chart repositories such as Ingress-Nginx. OpenFaaS for instance has always used its own repository and is not affected.
The following charts will have to be removed as apps, or re-sourced from upstream trusted publishers:
All other apps either use: a manifest or a CLI to install, and will not be affected.
If you are a user of arkade and need help, feel free to pitch in.
If you are the maintainer of the stable helm repo, perhaps this could have been communicated better? It was not clear that all artifacts were going to be immediately deleted. The mirror that was put up is also giving 404 errors, so that may need investigating too.
The text was updated successfully, but these errors were encountered: