diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-18 12:45:46 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-18 12:45:46 +0300 |
commit | a7b3560714b4d9cc4ab32dffcd1f74a284b93580 (patch) | |
tree | 7452bd5c3545c2fa67a28aa013835fb4fa071baf /doc/administration/geo/secondary_proxy/index.md | |
parent | ee9173579ae56a3dbfe5afe9f9410c65bb327ca7 (diff) |
Add latest changes from gitlab-org/gitlab@14-8-stable-eev14.8.0-rc42
Diffstat (limited to 'doc/administration/geo/secondary_proxy/index.md')
-rw-r--r-- | doc/administration/geo/secondary_proxy/index.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/administration/geo/secondary_proxy/index.md b/doc/administration/geo/secondary_proxy/index.md index ebd71757e91..c8dcbb81312 100644 --- a/doc/administration/geo/secondary_proxy/index.md +++ b/doc/administration/geo/secondary_proxy/index.md @@ -140,6 +140,18 @@ for details. To use TLS certificates with Let's Encrypt, you can manually point the domain to one of the Geo sites, generate the certificate, then copy it to all other sites. +## Behavior of secondary sites when the primary Geo site is down + +Considering that web traffic is proxied to the primary, the behavior of the secondary sites differs when the primary +site is inaccessible: + +- UI and API traffic return the same errors as the primary (or fail if the primary is not accessible at all), since they are proxied. +- For repositories that already exist on the specific secondary site being accessed, Git read operations still work as expected, + including authentication through HTTP(s) or SSH. +- Git operations for repositories that are not replicated to the secondary site return the same errors + as the primary site, since they are proxied. +- All Git write operations return the same errors as the primary site, since they are proxied. + ## Features accelerated by secondary Geo sites Most HTTP traffic sent to a secondary Geo site can be proxied to the primary Geo site. With this architecture, |