diff options
| author | Stan Hu <stanhu@gmail.com> | 2019-02-26 11:30:43 -0800 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2019-02-26 15:14:38 -0800 |
| commit | 7e209d86f4b88fbcd8cb5b1a8db85736e4e5e6b9 (patch) | |
| tree | af84b5f28db36f4039f8f9d1813400bce6ba6367 /doc/administration/high_availability | |
| parent | 3395eacb57285424b7b8d49bdf836f638af31e8c (diff) | |
| download | gitlab-ce-7e209d86f4b88fbcd8cb5b1a8db85736e4e5e6b9.tar.gz | |
Add documentation on upgrading GitLab HA nodes
As mentioned in
https://gitlab.com/gitlab-org/gitlab-ce/issues/58121#note_145299901, it
wasn't obvious that upgrading an GitLab HA cluster required special
care. Link to the Omnibus documentation for upgrade instructions.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58121
Diffstat (limited to 'doc/administration/high_availability')
| -rw-r--r-- | doc/administration/high_availability/gitlab.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/administration/high_availability/gitlab.md b/doc/administration/high_availability/gitlab.md index e554c06532e..d95c3acec54 100644 --- a/doc/administration/high_availability/gitlab.md +++ b/doc/administration/high_availability/gitlab.md @@ -146,6 +146,14 @@ the share is exported and exists on the NFS server and try to remount. --- +## Upgrading GitLab HA + +GitLab HA installations can be upgraded with no downtime, but the +upgrade process must be carefully coordinated to avoid failures. See the +[Omnibus GitLab multi-node upgrade +document](https://docs.gitlab.com/omnibus/update/#multi-node--ha-deployment) +for more details. + Read more on high-availability configuration: 1. [Configure the database](database.md) |