Charts: [stable/incubator] relocate package history

Created on 6 Oct 2020  路  6Comments  路  Source: helm/charts

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

  • [x] Archive Chart tarballs and re-index to new backup charts repo in GH Pages (https://github.com/helm/charts/issues/21103)
  • [x] Add repo archive notice to all non-deprecated charts (#24030)
  • [x] Mark all charts as deprecated (https://github.com/helm/charts/issues/24310)
  • [x] Create a redirect via index.yaml in the GCS buckets to point to GH Pages archive
    Users shouldn't see any failures at this point but will be pointing at the new archive location.
  • [x] Create a chart that has a known-missing required field - https://github.com/viglesiasce/deprecation-chart
  • [x] 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.

Additional context

Most helpful comment

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.

All 6 comments

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}}

    1. Edit the index.yaml to point all chart's urls fields to the location of that chart:

      yaml<br /> urls:</li> <li><a href="https://kubernetes-charts.storage.googleapis.com/deletion-notice-1.0.0.tgz">https://kubernetes-charts.storage.googleapis.com/deletion-notice-1.0.0.tgz</a><br />

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.

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.

 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.

Objects in the legacy buckets have now been marked private.

Was this page helpful?
0 / 5 - 0 ratings