This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

This issue is being automatically closed due to inactivity.

Are there any plans to migrate the stable/k8s-spot-termination-handler chart to another repo?

@axozoid
@egeland
@KierranM
@mariusv

@sudermanjr I don't mind taking it

@hareku
@mariusv
@srueg
any plan to migrate efs-provisioner? https://github.com/helm/charts/tree/master/stable/efs-provisioner

Moreover, even https://github.com/kubernetes-retired/external-storage/tree/master/aws/efs is retired and archived. 😞

There are alternatives? Maybe @wongma7

@olemarkus
@kennethaasan
any plan to migrate metrics-server? https://github.com/helm/charts/tree/master/stable/metrics-server

@jstriebel
any plan to migrate kube-slack? https://github.com/helm/charts/tree/master/stable/kube-slack

@desaintmartin
@Miouge1
any plan to migrate oauth2-proxy? https://github.com/helm/charts/tree/master/stable/oauth2-proxy

@olemarkus
@kennethaasan
any plan to migrate metrics-server? https://github.com/helm/charts/tree/master/stable/metrics-server

Currently tracked in kubernetes-sigs/metrics-server#572

oauth2-proxy: discussions here oauth2-proxy/oauth2-proxy#608

@verwilst
@davidkarlsen
any plan to migrate nfs-client-provisioner? https://github.com/helm/charts/tree/master/stable/nfs-client-provisioner

@hareku
@mariusv
@srueg
I was suggested to migrate to https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner
Ref: kubernetes-sigs/sig-storage-lib-external-provisioner#91
So I presume that efs-provisioner will be not supported.

@hareku
@mariusv
@srueg
I was suggested to migrate to https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner
Ref: kubernetes-sigs/sig-storage-lib-external-provisioner#91
So I presume that efs-provisioner will be not supported.

@pierluigilenoci that is bad news :-(

@scottrigby I saw you mentioned in another ticket that you had written up instructions for migrating a chart out of this repo into a new home (e.g. maintaining commit history and exposing it on artifact hub, i'm guessing). Looking through this issue and the repo I'm not finding those readily. Is it something you can share a link to?

@verwilst has agreed to pick up and maintain the Bookstack chart (BookStackApp/BookStack#2322 (comment)) and hoping to get them off to a good start :)

EDIT for posterity: I found these instructions, which I suspect is what Scott was referring to:

prometheus-community/helm-charts#3 (comment)

https://github.com/helm/charts-repo-actions-demo

nfs-client-provisioner and rocketchat are others i currently maintain, i'm willing to keep maintaining them in the future too.

@JoshKCarroll while migrating some charts I wrote this guide: https://github.com/torstenwalter/helm-chart-hosting

Can someone please confirm if this repo is still being archived, I am really unclear after the latest blog post: https://helm.sh/blog/new-location-stable-incubator-charts/

Do the existing OWNERS still need to move their charts?

@thesuperzapper confirmed. OWNERS still need to move their charts.

@pierluigilenoci then what are all those blog posts about, just the legacy versions?

@thesuperzapper
@mattfarina quote from https://kubernetes.slack.com/archives/C6E3XH1ED/p1603120675041800

There are two things. Being deprecated and being available. At Nov 13th the plan is still to deprecate the stable and incubator chart repos. The new location allows them to be accessible even after deprecation where we stop updating them.
We are working to find the charts new homes after the deprecation. Those will be discoverable on the artifact hub
Many of them have already moved but more than a few have not. I think we are talking about this situation on the Helm dev call this week.

@thesuperzapper I think this post explains it https://helm.sh/blog/new-location-stable-incubator-charts/
There are new locations for stable and incubator repositories hosting the already published charts.

Important Note: This does not affect the obsolescence timeline for the stable and incubator repositories that was announced in 2019. On November 13, 2020 the stable and incubator charts repository will reach the end of development and become archives. You can find that many of the charts have moved to other, community managed, repositories. You can discover these on the Artifact Hub. More information on the obsolescence will follow in future blog posts and communications.

@verwilst Do you have any idea when/where nfs-client-provisioner is likely to move? Do you know perhaps if K8s sig-storage plan to host a repo for the charts related to various such provisioners? (with/without the deprecated efs-provisioner)

Legal question here! Would that be okay to move from Apache 2 to MIT? oauth2-proxy is licenced under MIT and I suppose it would be easier to match destination licence.

Legal question here! Would that be okay to move from Apache 2 to MIT? oauth2-proxy is licenced under MIT and I suppose it would be easier to match destination licence.

@desaintmartin I have opened a CNCF service desk issue for this question. Let's wait to see where that goes.

@scottrigby oauth2-proxy status is missing from the table.

oauth2-proxy: discussions here oauth2-proxy/oauth2-proxy#608

I've relocated stable/docker-registry to twuni/docker-registry and published this repo and chart to Artifact Hub for the community to use. I hope that's okay. Happy to defer to an "official" chart if/when the time comes. Just bridging the gap as best I can, since a migration for it doesn't appear to have been picked up, yet.

Links

• Source: https://github.com/twuni/docker-registry.helm
• Artifact Hub: https://artifacthub.io/packages/helm/twuni/docker-registry

@tcarmet @miniscruff @alexanderchan-scality @JorenZ @DandyDeveloper any plan to migrate the redis-ha chart somewhere? Is the new chart position one of these two?

• https://github.com/scality/Zenko/tree/development/1.0/kubernetes/zenko/charts/redis-ha
• https://github.com/DandyDeveloper/charts/tree/master/charts/redis-ha

@pierluigilenoci Redis-ha has been migrated to: https://github.com/DandyDeveloper/charts/tree/master/charts/redis-ha (Per the deprecation message in the chart itself).

Thank you for asking!

@pierluigilenoci Redis-ha has been migrated to: DandyDeveloper/charts@master/charts/redis-ha (Per the deprecation message in the chart itself).

Thank you @DandyDeveloper
@scottrigby the table need to be update 😄

Hi everyone. I have been dealing with a family emergency the past few weeks.

We will want to update the table/list above to help people find the new home(s) for these charts. But we'll need to find a different way to determine this moving forward since this repo code will no longer be updated, notices will no longer be added to each charts readme as it was before.

Generally speaking, Charts are now discoverable in the CNCF Artifact Hub (https://artifacthub.io/).

Maintainers of distributed chart repos are encouraged to:

• list their repos in the Artifact Hub
• follow the Charts Best Practices Guide
• for greater reliability, integrate automated Helm Chart Testing (though Helm chart repo GitHub Actions or otherwise)
• when releasing charts (whether using Helm Chart Releaser, the wrapping GitHub Action, or otherwise), ensure versioned packages are immutable (any changes, however small, should be a new version). For greater community reliability, please continue to follow Semantic Versioning
• when adopting chart source code for new development, please carry over git history. @torstenwalter compiled a good step-by-step guide based on work I and he had done on this for various community chart repos: https://github.com/torstenwalter/helm-chart-hosting. Please follow that as best as you can.
• The Artifact Hub allows you to verify chart repo ownership, and there is also a process for marking a chart "official" there. Official charts are maintained (or approved) by the maintainers of the application the chart installs. This doesn't mean other charts are bad to use - for example, Bitnami had for years maintained many of the community charts in this repo, and now continue to do so now in their own distributed chart repo, and are still equally trustworthy. This is just to help users navigate, and make up their own minds about the trustworthiness of each chart repo and chart. As always, users are encouraged to review a chart's code before installing it.

If anyone has other ideas about how this issue can be more useful to end users and maintainers alike, please let me know and we can do whatever we need to to help the community. The charts maintainers who formerly managed this repo are still active in working on tools to help the wider Helm charts community. Thank you all for the continued community. It has not ended, it is simply bigger than ever before and has required moving to new, distributed hosting, discovery, and tooling.

@scottrigby thanks so much for the explanation and for your time!

IMHO, beside continuing to keep this issue open by updating the table, I see no other way to give more information to the community.

At the end, if all the charts that have not migrated within the dealine remain without precise indications, it is to be attributed to the maintainers who have not acted before. For the charts I use I tried to push the maintainers but more than asking, it couldn't be done. So that's okay too.

Quick update here,

stable/coredns is Done via https://github.com/coredns/helm/
stable/kube-state-metrics is Done via https://github.com/kubernetes/kube-state-metrics/tree/master/charts/kube-state-metrics

minio is actually now hosted at https://helm.min.io

I've done clamav, https://artifacthub.io/packages/search?page=1&ts_query_web=clamav

Folks, any plans to fix stable/openvpn? Thanks

Folks, any plans to fix stable/openvpn? Thanks

There are several charts at https://artifacthub.io/packages/search?page=1&ts_query_web=openvpn, maybe there's one that fits your needs.

If you need the original stable/openvpn, you could try hosting it and publishing it in the Artifact Hub ! ;)

BTW, not sure if this is still relevant to post it here, but I moved/updated stable/karma as well: https://artifacthub.io/packages/search?page=1&ts_query_web=karma

stable/pomerium was officially done under helm/charts#24378. New home is https://helm.pomerium.io/.

Hi again everyone 👋 Just moved this issue to the Helm Community repo, as we're closing out the lifecycle/frozen issues from the no longer supported https://github.com/helm/charts/ repo.

This issue still serves two needs I'm aware of:

1. Points end users to new locations for the now archived versions of stable or incubator charts (the releases prior to November 13, 2020, which have since been generously hosted by GitHub), so that they can upgrade to newer and currently maintained versions.
2. Helps previous and/or potential new chart maintainers coordinate where to continue maintaining the chart source and repo automation tooling for each chart (or set of charts) as a community. Thanks for your continuing work on Helm charts! ✨

We will keep this issue open until these needs are solved in another way, or are no longer necessary to solve, whichever comes first 🤝

I noticed that GitHub Issues on the helm/charts repo has been disabled. Unfortunately this means existing links to issues in code comments now lead to 404 pages, like this one: helm/charts#14390. Is it possible to re-enable Issues for historical purposes but prevent new issues or comments from being created, so that links continue to work? This should be possible using the "archive repository" feature on GitHub. Or make an export of issues so that the historical content remains accessible?

@elliottsj Thank you, re-enabled issues for issue archive access, and re-archived the repo 👍

📣 Hi everyone, the checklist has been moved from the top of this issue description to a file in the community repo so the community can help maintain this through PRs.
https://github.com/helm/community/blob/main/stable-repo-charts-new-locations.md

It's likely I have missed some of the comments in this issue or issues/PRs that link to this issue that contain info on updated chart sources. Please help us update this document through pull requests to helm/community 😄

📌 pinning this in the issue description to make current status easier to find 🕵️