| stage | group | info |
|---|---|---|
Systems |
Distribution |
To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments |
This document serves as a guide to create a strong plan to upgrade a self-managed GitLab instance.
General notes:
- If possible, we recommend you test out the upgrade in a test environment before updating your production instance. Ideally, your test environment should mimic your production environment as closely as possible.
- If working with Support
to create your plan, share details of your architecture, including:
- How is GitLab installed?
- What is the operating system of the node? (check OS versions that are no longer supported to confirm that later updates are available).
- Is it a single-node or a multi-node setup? If multi-node, share any architectural details about each node with us.
- Are you using GitLab Geo? If so, share any architectural details about each secondary node.
- What else might be unique or interesting in your setup that might be important for us to understand?
- Are you running into any known issues with your current version of GitLab?
Immediately before and after the upgrade, perform the pre-upgrade and post-upgrade checks to ensure the major components of GitLab are working:
-
Check the general configuration:
sudo gitlab-rake gitlab:check
-
Confirm that encrypted database values can be decrypted:
sudo gitlab-rake gitlab:doctor:secrets
-
In GitLab UI, check that:
- Users can sign in.
- The project list is visible.
- Project issues and merge requests are accessible.
- Users can clone repositories from GitLab.
- Users can push commits to GitLab.
-
For GitLab CI/CD, check that:
- Runners pick up jobs.
- Docker images can be pushed and pulled from the registry.
-
If using Geo, run the relevant checks on the primary and each secondary:
sudo gitlab-rake gitlab:geo:check
-
If using Elasticsearch, verify that searches are successful.
-
If you are using Reply by Email or Service Desk, manually install the latest version of
gitlab-mail_room:gem install gitlab-mail_room
NOTE: This step is necessary to avoid thread deadlocks and to support the latest MailRoom features. See this explanation for more details.
If in any case something goes wrong, see how to troubleshoot.
It's possible that something may go wrong during an upgrade, so it's critical that a rollback plan be present for that scenario. A proper rollback plan creates a clear path to bring the instance back to its last working state. It is comprised of a way to back up the instance and a way to restore it.
Create a backup of GitLab and all its data (database, repositories, uploads, builds, artifacts, LFS objects, registry, pages). This is vital for making it possible to roll back GitLab to a working state if there's a problem with the upgrade:
- Create a GitLab backup. Make sure to follow the instructions based on your installation method. Don't forget to back up the secrets and configuration files.
- Alternatively, create a snapshot of your instance. If this is a multi-node installation, you must snapshot every node. This process is out of scope for GitLab Support.
If you have a test environment that mimics your production one, we recommend testing the restoration to ensure that everything works as you expect.
To restore your GitLab backup:
- Before restoring, make sure to read about the prerequisites, most importantly, the versions of the backed up and the new GitLab instance must be the same.
- Restore GitLab. Make sure to follow the instructions based on your installation method. Confirm that the secrets and configuration files are also restored.
- If restoring from a snapshot, know the steps to do this. This process is out of scope for GitLab Support.
For the upgrade plan, start by creating an outline of a plan that best applies to your instance and then upgrade it for any relevant features you're using.
- Generate an upgrade plan by reading and understanding the relevant documentation:
- upgrade based on the installation method:
- Zero-downtime upgrades (if possible and desired)
- Convert from GitLab Community Edition to Enterprise Edition
- What version should you upgrade to:
- Determine what upgrade path to follow.
- Account for any version-specific update instructions for both the current version and the destination version.
- Account for any version-specific changes.
- Check the OS compatibility with the target GitLab version.
- Due to background migrations, plan to pause before any further upgrades. All migrations must finish running before the next upgrade.
- If available in your starting version, consider turning on maintenance mode during the upgrade.
- About PostgreSQL:
- On the top bar, select Main menu > Admin, and look for the version of PostgreSQL you are using. If a PostgreSQL upgrade is needed, account for the relevant packaged or non-packaged steps.
Apart from all the generic information above, you may have enabled some features that require special planning.
Feel free to ignore sections about features that are inapplicable to your setup, such as Geo, external Gitaly, or Elasticsearch.
If you're using an external Gitaly server, it must be upgraded to the newer version prior to upgrading the application server.
If you're using Geo:
- Review Geo upgrade documentation.
- Read about the Geo version-specific update instructions.
- Review Geo-specific steps when upgrading the database.
- Create an upgrade and rollback plan for each Geo site (primary and each secondary).
After updating GitLab, upgrade your runners to match your new GitLab version.
If you have Kubernetes clusters connected with GitLab, upgrade your GitLab agents for Kubernetes to match your new GitLab version.
Before updating GitLab, confirm advanced search migrations are complete by checking for pending advanced search migrations.
After updating GitLab, you may have to upgrade Elasticsearch if the new version breaks compatibility. Updating Elasticsearch is out of scope for GitLab Support.
If anything doesn't go as planned:
- If time is of the essence, copy any errors and gather any logs to later analyze, and then roll back to the last working version. You can use the following tools to help you gather data:
- For support:
- Contact GitLab Support and, if you have one, your Customer Success Managers.
- If the situation qualifies and your plan includes emergency support, create an emergency ticket.