diff options
author | Achilleas Pipinellis <axil@gitlab.com> | 2019-05-23 22:01:48 +0000 |
---|---|---|
committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-05-23 22:01:48 +0000 |
commit | 535b3d73413ba007eb1812f86772b93ead24f7d6 (patch) | |
tree | bc1e14f2ebf3d47ff0b9605bbf98809563e76428 | |
parent | 26c985089628b397a3df1816142da1486c1a7e34 (diff) | |
parent | 85a8efd1b1f115546157fdab0834436d9025ce6d (diff) | |
download | gitlab-ce-535b3d73413ba007eb1812f86772b93ead24f7d6.tar.gz |
Merge branch 'docs/ssot_geo_nodes' into 'master'
Edit Geo nodes content to comply with SSOT guidelines
See merge request gitlab-org/gitlab-ce!28519
-rw-r--r-- | doc/user/admin_area/geo_nodes.md | 22 |
1 files changed, 19 insertions, 3 deletions
diff --git a/doc/user/admin_area/geo_nodes.md b/doc/user/admin_area/geo_nodes.md index 776ab139c64..fb0f9a3285d 100644 --- a/doc/user/admin_area/geo_nodes.md +++ b/doc/user/admin_area/geo_nodes.md @@ -1,9 +1,13 @@ +--- +type: howto +--- + # Geo nodes admin area **[PREMIUM ONLY]** -For more information about setting up GitLab Geo, read the -[Geo documentation](https://docs.gitlab.com/ee/administration/geo/replication/index.html). +You can configure various settings for GitLab Geo nodes. For more information, see +[Geo documentation](https://docs.gitlab.com/ee/administration/geo/replication/index.md). -When you're done, you can navigate to **Admin area > Geo** (`/admin/geo/nodes`). +On the primary node, go to **Admin area > Geo**. On secondary nodes, go to **Admin area > Geo > Nodes**. ## Common settings @@ -68,3 +72,15 @@ a unique `name` is set for each Geo node. The `gitlab.rb` setting The load balancer must use sticky sessions in order to avoid authentication failures and cross site request errors. + +<!-- ## Troubleshooting + +Include any troubleshooting steps that you can foresee. If you know beforehand what issues +one might have when setting this up, or when something is changed, or on upgrading, it's +important to describe those, too. Think of things that may go wrong and include them here. +This is important to minimize requests for support, and to avoid doc comments with +questions that you know someone might ask. + +Each scenario can be a third-level heading, e.g. `### Getting error message X`. +If you have none to add when creating a doc, leave this section in place +but commented out to help encourage others to add to it in the future. -->
\ No newline at end of file |