diff options
Diffstat (limited to 'doc/update/plan_your_upgrade.md')
| -rw-r--r-- | doc/update/plan_your_upgrade.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/update/plan_your_upgrade.md b/doc/update/plan_your_upgrade.md index 406f8322218..320f900dd21 100644 --- a/doc/update/plan_your_upgrade.md +++ b/doc/update/plan_your_upgrade.md @@ -4,7 +4,7 @@ group: Distribution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments --- -# Create a GitLab upgrade plan +# Create a GitLab upgrade plan **(FREE SELF)** This document serves as a guide to create a strong plan to upgrade a self-managed GitLab instance. @@ -75,7 +75,7 @@ Create a backup of GitLab and all its data (database, repos, 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](../raketasks/backup_restore.md#back-up-gitlab). +- Create a [GitLab backup](../raketasks/backup_restore.md). Make sure to follow the instructions based on your installation method. Don't forget to back up the [secrets and configuration files](../raketasks/backup_restore.md#storing-configuration-files). - Alternatively, create a snapshot of your instance. If this is a multi-node @@ -173,7 +173,7 @@ If anything doesn't go as planned: - [`kubesos`](https://gitlab.com/gitlab-com/support/toolbox/kubesos/) if you installed GitLab using the Helm Charts. - For support: - - [Contact GitLab Support](https://support.gitlab.com) and, + - [Contact GitLab Support](https://support.gitlab.com/hc) and, if you have one, your Technical Account Manager. - If [the situation qualifies](https://about.gitlab.com/support/#definitions-of-support-impact) and [your plan includes emergency support](https://about.gitlab.com/support/#priority-support), |