Merge branch 'jramsay-4264-geo-ip-docs' into 'master'

Add explicit GCP private address docs to geo

Closes #4264

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

doc/gitlab-geo/database.md

@@ -109,13 +109,7 @@ The following guide assumes that:
     each node. Note: For external PostgreSQL instances, see [additional instructions][external postgresql].
 
     If you are using a cloud provider, you can lookup the addresses for each
-    Geo node through your cloud provider's management console. A table of common
-    terminology is provided below as it varies between vendors.
-
-    | GitLab Terminology | Amazon Web Services | Google Cloud Platform |
-    |-----|-----|-----|-----|
-    | Private address | Private address | Internal address |
-    | Public address | Public address | External address |
+    Geo node through your cloud provider's management console.
 
     To lookup the address of a Geo node, SSH in to the Geo node and execute:
 
@@ -140,6 +134,11 @@ The following guide assumes that:
     | `postgresql['trust_auth_cidr_addresses']` | Primary's private address |
     | `postgresql['md5_auth_cidr_addresses']` | Secondary's public addresses |
 
+    If you are using Google Cloud Platform, SoftLayer, or any other vendor that
+    provides a virtual private cloud you can use the secondary's private
+    address (corresponds to "internal address" for Google Cloud Platform) for
+    `postgresql['md5_auth_cidr_addresses']`.
+
     The `listen_address` option opens PostgreSQL up to network connections
     with the interface corresponding to the given address. See [the PostgreSQL
     documentation](https://www.postgresql.org/docs/9.6/static/runtime-config-connection.html)