+Vic Iglesias Right. There are Googlers who can grant additional permissions, but moving the Project would fix this completely. Vic had another suggestion: is it possible to redirect via Helm index

To be clear, what I was suggesting was not intended to “mess with anyone’s plans” - I was simply trying to lay out that if Helm finds itself in a difficult position here, we (TOC) are here to

Sorry for the confusion. I've asked multiple people at Google about this and I was told it wasn't possible. Thank you for not only clearing up the confusion but pointing out the project-migration

That's not correct. Who told you that? As I pointed out on https://github.com/helm/community/issues/114: https://cloud.google.com/resource-manager/docs/project-migration Transferring the GCP Project

From what I have been told, it's not technically possible to transfer the project. To add some context about cost and history... We have seen numbers on what it would cost to host these through Google

All we need from Google is for them to redirect the chart repository domain name to a new location. That is the only thing that is currently causing the high-probability risk of the chart repositories

My question is: is the *Helm project* asking for the CNCF to fund extended storage for these charts, or not? (assuming this is technically possible). I can see why the answer might be "not"; we have

Josh, You ask a good question. There are two things worth noting... Many of the charts people use have been slower to move out of the stable and incubator repos than expected. We are still finding

All, I'm really unclear on why CNCF would devote resources to maintaining a set of outdated Helm charts if the Helm project itself has decided not to do so. Wouldn't it be more sensible for us to

+MattButcher --brendan

This has been an issue since at least April 2019. The deprecation message is not getting through.

Thanks Chris. Just noting that we do have the Special Issues process where $$$ are involved to take technical budget issues to the GB, though it sounds unlikely that this would be an affordable item

It would be great to have input from the current Helm maintainers on their issue and public deprecation plan here. +Matt Farina Also, this is a big budget item and will likely involve the GB, where

The affected charts are mainly the ones in the official community repo: https://github.com/helm/charts There is a notice in the README. PRs to the charts are still being merged, though at a lower

It does seem like a hard cut-off is going to hurt people without some further action. I can see two ways the CNCF might be able to help: - Getting the word out. I suspect that a lot of Helm chart

I would recommend setting up a URL forwarding from old repos to new repos, so that charts are maintained at new locations but old URL references continue to work. Thanks, -Arvind

TOC Folks, I want to bring https://github.com/helm/community/issues/114 to your attention. This has the potential for causing a lot of pain to users. The buckets are scheduled to be deleted on Nov 13,

+1 binding -- ~Dave

I am using this list as it most likely reaches the widest audience in the CNCF. In recent discussions in the app delivery SIG we came to the conclusion that a reference application would make

+1 NB. As the lead reviewer for the upcoming sig-security assessment, the project appears to have done a fair amount of due diligence from a precursory look at the prepared draft. Andres