Merge branch 'docs-repo-merge-8-admin-ha-ee' into 'master'

Docs: (EE Port) Merge EE doc/administration/high_availability to CE

See merge request gitlab-org/gitlab-ee!12107

doc/administration/high_availability/README.md

@@ -135,7 +135,7 @@ the contention.
 - 2 or more GitLab application nodes (Unicorn, Workhorse, Sidekiq, PGBouncer)
 - 1 NFS/Gitaly server
 
-![Horizontal architecture diagram](../img/high_availability/horizontal.png)
+![Horizontal architecture diagram](https://docs.gitlab.com/ee/administration/img/high_availability/horizontal.png)
 
 ### Hybrid
 
@@ -151,7 +151,7 @@ contention due to certain workloads.
 - 2 or more Web nodes (Unicorn, Workhorse, PGBouncer)
 - 1 or more NFS/Gitaly servers
 
-![Hybrid architecture diagram](../img/high_availability/hybrid.png)
+![Hybrid architecture diagram](https://docs.gitlab.com/ee/administration/img/high_availability/hybrid.png)
 
 ### Fully Distributed
 
@@ -170,7 +170,7 @@ with the added complexity of many more nodes to configure, manage and monitor.
 - 2 or more Web nodes (All other web requests)
 - 2 or more NFS/Gitaly servers
 
-![Fully Distributed architecture diagram](../img/high_availability/fully-distributed.png)
+![Fully Distributed architecture diagram](https://docs.gitlab.com/ee/administration/img/high_availability/fully-distributed.png)
 
 The following pages outline the steps necessary to configure each component
 separately:

doc/administration/high_availability/pgbouncer.md

@@ -13,6 +13,7 @@ It is recommended to run pgbouncer alongside the `gitlab-rails` service, or on i
 ## Operations
 
 ### Running Pgbouncer as part of an HA GitLab installation
+
 See our [HA documentation for PostgreSQL](database.md) for information on running pgbouncer as part of a HA setup
 
 ### Running Pgbouncer as part of a non-HA GitLab installation