Maintaining the upgrade stop in the charts project

The GitLab chart creates a pre-upgrade hook that checks if the upgrade follows a valid upgrade path.

If the upgrade path is invalid, the upgrade will be aborted.

To apply a new upgrade stop:

A new upgrade stop must be applied in the next minor release. For example, the 16.3 upgrade stop must be merged into 16.4.
Change MIN_VERSION and CHART_MIN_VERSION in templates/_runcheck.tpl.
Update the test cases in scripts/debug/test_runcheck.sh.
Confirm that the test cases pass.

Help & feedback

Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.

Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Join First Look to help shape new features.

View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).