Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/incubator] relocate package history #23850

Closed
6 tasks done
scottrigby opened this issue Oct 6, 2020 · 8 comments
Closed
6 tasks done

[stable/incubator] relocate package history #23850

scottrigby opened this issue Oct 6, 2020 · 8 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@scottrigby
Copy link
Member

scottrigby commented Oct 6, 2020

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

Additional context

@scottrigby scottrigby pinned this issue Oct 14, 2020
@scottrigby scottrigby changed the title stable/incubator package history [stable/incubator] package history Oct 14, 2020
@scottrigby scottrigby changed the title [stable/incubator] package history [stable/incubator] relocate package history Oct 14, 2020
@viglesiasce
Copy link
Contributor

Another option that shuts down the repos but at least gives users one final pointer would be to:

  1. Create a chart with a required field that would most definitely not be set in any chart:
     {{ required "This repo has been shut down. Please read our guidance here:https://github.com/helm/charts#deprecation-timeline!" .Values.thisRepoHasBeenShutDown}}
    
  2. Edit the index.yaml to point all chart's urls fields to the location of that chart:
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.

@paulczar
Copy link
Collaborator

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.

@viglesiasce
Copy link
Contributor

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.

@scottrigby
Copy link
Member Author

@viglesiasce
Copy link
Contributor

viglesiasce commented Dec 16, 2020

 Replace all existing tarball urls in the GCS index.yaml to point to the deprecation chart.
This will give users an error message pointing them in the right direction to fix their issues.

This was done today.

@viglesiasce
Copy link
Contributor

Objects in the legacy buckets have now been marked private.

@stale
Copy link

stale bot commented Jul 21, 2021

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.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 21, 2021
@stale
Copy link

stale bot commented Jan 9, 2022

This issue is being automatically closed due to inactivity.

@stale stale bot closed this as completed Jan 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants