Skip to content

Commit 33df642

Browse files
niskhakova-gitlaberead
authored andcommitted
Expand guidance for trust_auth_cidr_addresses
for multi-node setups Signed-off-by: Nailia Iskhakova <[email protected]>
1 parent e314a45 commit 33df642

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

doc/settings/database.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -307,9 +307,10 @@ The following settings are affected in the `postgresql` block:
307307
- `md5_auth_cidr_addresses`: A list of CIDR address blocks that are allowed to
308308
connect to the server, after authentication with a password.
309309
- `trust_auth_cidr_addresses`: A list of CIDR address blocks that are allowed
310-
to connect to the server, without authentication of any kind. _Be very careful
311-
with this setting._ It's suggested that this be limited to the loopback
312-
address of `127.0.0.1/24` or even `127.0.0.1/32`.
310+
to connect to the server, without authentication of any kind. You should
311+
only set this setting to allow connections from nodes that need to connect,
312+
such as GitLab Rails or Sidekiq. This includes local connections when deployed
313+
on the same node or from components such as Postgres Exporter (`127.0.0.1/32`).
313314
- `sql_user`: Controls the expected username for MD5 authentication. This
314315
defaults to `gitlab`, and isn't a required setting.
315316
- `sql_user_password`: Sets the password that PostgreSQL will accept for MD5

0 commit comments

Comments
 (0)