-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[stable/incubator] relocate package history #23850
Comments
Another option that shuts down the repos but at least gives users one final pointer would be to:
urls:
- https://kubernetes-charts.storage.googleapis.com/deletion-notice-1.0.0.tgz The behavior would be that when someone try's to install and or upgrade an existing chart they would get a hard failure that would print out the error message that we crafted and point them at more details on what they can do to fix. There would still be costs involved here however so we'd want to continue to optimize in that dimension where possible. |
from Helm Call, I would love to deprecate every chart on Nov 13 ( as in set deprecated: true ) and we should set warnings in NOTES.txt in all charts ASAP to mention the chart repo url is moving and the chart will be deprecated and no changes accepted as of Nov 13. |
I added this to the solution timeline. |
This was done today. |
Objects in the legacy buckets have now been marked private. |
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. |
Problem
Once the stable/incubator chart repos are marked obsolete, and this git repo is archived, the package history from these repos are planned to be garbage collected. Users who are not able to upgrade to newer versions will fail when attempting to pull/install/upgrade etc previous versions.
Status
The Helm team is working on an official recommendation. Subscribe to this issue for updates.
Solution Timeline
Users shouldn't see any failures at this point but will be pointing at the new archive location.
This will give users an error message pointing them in the right direction to fix their issues.
Additional context
The text was updated successfully, but these errors were encountered: