diff options
| author | Evan Read <eread@gitlab.com> | 2019-08-30 01:48:28 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-08-30 01:48:28 +0000 |
| commit | fad993d2540bbf2c4ece691d1109840286cf5b7d (patch) | |
| tree | f01fc28ed3c77e23c55fc5f79c88c6f141cbbeba | |
| parent | 1892c8de311956dfe5032b8c25a6b7aae64f4986 (diff) | |
| download | gitlab-ce-fzimmer-master-patch-75127.tar.gz | |
Apply suggestion to doc/administration/geo/replication/updating_the_geo_nodes.mdfzimmer-master-patch-75127
| -rw-r--r-- | doc/administration/geo/replication/updating_the_geo_nodes.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/administration/geo/replication/updating_the_geo_nodes.md b/doc/administration/geo/replication/updating_the_geo_nodes.md index 36b9ef4e6da..ef70f7b613f 100644 --- a/doc/administration/geo/replication/updating_the_geo_nodes.md +++ b/doc/administration/geo/replication/updating_the_geo_nodes.md @@ -6,7 +6,8 @@ Depending on which version of Geo you are updating to/from, there may be differe NOTE: **Note:** These general update steps are not intended for [high-availability deployments](https://docs.gitlab.com/omnibus/update/README.html#multi-node--ha-deployment), and will cause downtime. If you want to avoid downtime, consider using [zero downtime updates](https://docs.gitlab.com/omnibus/update/README.html#zero-downtime-updates). -In order to update the Geo nodes when a new GitLab version is released, you need to update the **primary** and all **secondary** nodes: +To update the Geo nodes when a new GitLab version is released, update **primary** +and all **secondary** nodes: 1. Log into the **primary** node. 1. [Update GitLab on the **primary** node using Omnibus](https://docs.gitlab.com/omnibus/update/README.html). |