Commit 98b5d131 authored by James Ramsay's avatar James Ramsay

Add explicit GCP private address docs to geo

parent b4e093ae
......@@ -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,9 @@ 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 or SoftLayer, you can use the
secondary's private address.
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)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment