Geo - rake gitlab:geo:check complains if you don't have PG streaming replication set up

Summary

Running the gitlab:geo:check rake task complains on a Geo secondary site if you don't have PostgreSQL database replication enabled.

What is the current behavior?

$ bundle exec rails gitlab:geo:check

Checking Geo ...

GitLab Geo tracking database is correctly configured ... yes
Database replication enabled? ... no
  Try fixing it:
  Follow Geo setup instructions to configure primary and secondary nodes for replication
  For more information see:
  http://127.0.0.1:3001/help/administration/geo/setup/database
Database replication working? ... no
  Try fixing it:
  Follow Geo setup instructions to configure primary and secondary nodes for replication
  For more information see:
  http://127.0.0.1:3001/help/administration/geo/setup/database
GitLab Geo HTTP(S) connectivity ...
* Can connect to the primary node ... no
GitLab Geo secondary Git SSH port is the same as the primary ... yes
GitLab Geo is available ...
GitLab Geo is enabled ... yes
This machine's Geo node name matches a database record ... yes, found a secondary node named "gdk-geo"
HTTP/HTTPS repository cloning is enabled ... yes
Machine clock is synchronized ... yes
Git user has default SSH configuration? ... yes
OpenSSH configured to use AuthorizedKeysCommand ... yes
GitLab configured to disable writing to authorized_keys file ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes

Checking Geo ... Finished

What is the expected correct behavior?

The gitlab:geo:check should not complain and exit successfully if no PostgreSQL database replication is enabled.