From a3376481122dc4bbc7d9722c53b6f2173f494f0a Mon Sep 17 00:00:00 2001 From: keelanlang Date: Tue, 29 Aug 2023 16:34:44 -0400 Subject: [PATCH 1/2] Update language for geo ref arch --- doc/administration/reference_architectures/index.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/doc/administration/reference_architectures/index.md b/doc/administration/reference_architectures/index.md index 0c38be275482b7..ed216f4a56d189 100644 --- a/doc/administration/reference_architectures/index.md +++ b/doc/administration/reference_architectures/index.md @@ -107,9 +107,16 @@ This is an alternative and more **advanced** setup compared to a standard Refere ### GitLab Geo (Cross Regional Distribution / Disaster Recovery) -With [GitLab Geo](../geo/index.md) you can have both distributed environments in different regions and a full Disaster Recovery (DR) setup in place. With this setup you would have 2 or more separate environments, with one being a primary that gets replicated to the others. In the rare event the primary site went down completely you could fail over to one of the other environments. - -This is an **advanced and complex** setup and should only be undertaken if you have DR as a key requirement. Decisions then on how each environment are configured would also need to be taken, such as if each environment itself would be the full size and / or have HA. +With [GitLab Geo](../geo/index.md), you can achieve distributed environments in +different regions with a full Disaster Recovery (DR) setup in place. GitLab Geo +requires at least two separate environments: one primary site, and one or more +secondary sites that serve as replicas. In the event the primary site becomes +unavailable, you can fail over to one of the secondary sites. + +This is an **advanced and complex** setup and should only be undertaken if DR is +a key requirement for your environment. You must also make additional decisions +on how each site is configured, such as if each secondary site would be the +same architecture as the primary, or if each site is configured for HA. ### Cloud provider services -- GitLab From fec667105a6e2bcb5cc5bdede9e3fe2d71e4a459 Mon Sep 17 00:00:00 2001 From: Evan Read Date: Tue, 29 Aug 2023 23:48:33 +0000 Subject: [PATCH 2/2] Apply 2 suggestion(s) to 1 file(s) --- doc/administration/reference_architectures/index.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/doc/administration/reference_architectures/index.md b/doc/administration/reference_architectures/index.md index ed216f4a56d189..51409c8a056a15 100644 --- a/doc/administration/reference_architectures/index.md +++ b/doc/administration/reference_architectures/index.md @@ -109,13 +109,16 @@ This is an alternative and more **advanced** setup compared to a standard Refere With [GitLab Geo](../geo/index.md), you can achieve distributed environments in different regions with a full Disaster Recovery (DR) setup in place. GitLab Geo -requires at least two separate environments: one primary site, and one or more -secondary sites that serve as replicas. In the event the primary site becomes -unavailable, you can fail over to one of the secondary sites. +requires at least two separate environments: -This is an **advanced and complex** setup and should only be undertaken if DR is +- One primary site. +- One or more secondary sites that serve as replicas. + +If the primary site becomes unavailable, you can fail over to one of the secondary sites. + +This **advanced and complex** setup should only be undertaken if DR is a key requirement for your environment. You must also make additional decisions -on how each site is configured, such as if each secondary site would be the +on how each site is configured, such as if each secondary site would be the same architecture as the primary, or if each site is configured for HA. ### Cloud provider services -- GitLab