PROCESSES.md
This document outlines processes and procedures for some common tasks in the charts repository.
When a chart is no longer maintained it can be deprecated. Once a chart is deprecated the expectation is the chart will see no further development. The chart and its versions will still be accessible, though tools such as monocular and Kubeapps Hub will no longer list the chart.
To deprecate a chart perform the following:
version in the Chart.yaml file. This is required as all charts are immutable.Chart.yaml file of deprecated: true at the top level of the YAML structure.For example, A Chart.yaml could start like:
name: foo
# The foo chart is deprecated and no longer maintained. For details deprecation,
# including how to un-deprecate a chart see the PROCESSES.md file.
deprecated: true
description: DEPRECATED foo bar baz qux...
When new maintainers are interested in bring a chart out of deprecation with new features or new support that can be an option. To un-deprecate a chart:
Chart.yaml file should be removed along with any associated comment.version needs to be incremented accordingly. If the same functionality is kept the version can be a patch increase. Otherwise the minor or major version needs to be incremented. For more detail on changing the version number see the semver specification.When promoting a chart from incubator to stable there are several steps that need to be carried out.
version will, also, need to be incremented.There are two parts to reviewing a pull request in the process to do so and the guidelines to follow. Both of those are outlined in the Review Guidelines.