Upgrade Guide

Before upgrading your GitLab installation, you need to check the changelog corresponding to the specific release you want to upgrade to and look for any release notes that might pertain to the new GitLab chart version.

Warning: Warning: If you are upgrading from the 1.x version of the chart to the latest, you need to first update to the latest 1.9.x patch release in order for the upgrade to work. The 2.0 release notes describe the supported upgrade path.

We also recommend that you take a backup first. Also note that you need to provide all values using helm upgrade --set key=value syntax or -f values.yml instead of using --reuse-values because some of the current values might be deprecated.

Note: You can retrieve your previous --set arguments cleanly, with helm get values <release name>. If you direct this into a file (helm get values <release name> > gitlab.yaml), you can safely pass this file via -f. Thus helm upgrade gitlab gitlab/gitlab -f gitlab.yaml. This safely replaces the behavior of --reuse-values

Mappings between chart versioning and GitLab versioning can be found here.


The following are the steps to upgrade GitLab to a newer version:

  1. Check the change log for the specific version you would like to upgrade to
  2. Go through deployment documentation step by step
  3. Extract your previous --set arguments with

    helm get values gitlab > gitlab.yaml
  4. Decide on all the values you need to set
  5. If you would like to use the GitLab operator go through the steps outlined in Operator installation
  6. Perform the upgrade, with all --set arguments extracted in step 4

    helm upgrade gitlab gitlab/gitlab \
      --version <new version> \
      -f gitlab.yaml \
      --set ...