Add direct connection configuration to praefect

Details

• Point of contact for this request: @8bitlife
• If a call is needed, what is the proposed date and time of the call: please direct message to me in Slack @Pavlo Strokov

SRE Support Needed

In order to better support reads distribution feature of the gitaly/praefect setup we need to configure direct connection link between praefect and its database.

host_no_proxy = "YYY"
port_no_proxy = XXX

Required changes already done in omnibus and now it needs to be configured properly on our environments. By the direct connection means there should be no PgBouncer or other type of proxy in between that could block or restrict LISTEN/NOTIFY operations of the PostgresQL database.

To verify configurations were properly set you should see reads distribution caching is enabled by configuration in the log after praefect restart.

Related to: gitlab-org/gitaly#3053 (closed)

Acceptance criteria

• All praefect nodes in staging have database_host_no_proxy and database_port_no_proxy pointing at the staging praefect database: https://ops.gitlab.net/gitlab-cookbooks/chef-repo/-/merge_requests/4735
• "read distribution caching is enabled by configuration" messages appear on the logs for all staging praefect hosts
• All praefect nodes in production have database_host_no_proxy and database_port_no_proxy pointing at the production praefect database: https://ops.gitlab.net/gitlab-cookbooks/chef-repo/-/merge_requests/4777
• "read distribution caching is enabled by configuration" messages appear on the logs for all production praefect hosts