Postgres slave in 5 node deployment generates - no pg_hba.conf entry for replication

Google Cloud Apigee
1

Edge Private Cloud 4.18.05

5 node deployment topology -

[https://docs.apigee.com/private-cloud/v4.18.05/installation-topologies#5hostclusteredinstallation](https://docs.apigee.com/private-cloud/v4.18.05/installation-topologies#5hostclusteredinstallation)

All nodes start up except node 5 (PG slave). Error:

connection to postgres master successful. Proceeding with replication setup on standby
ls: cannot access /appdata/apigee/data/apigee-postgresql/pgdata/: No such file
or directory
apigee-service: apigee-postgresql: Not running (NO_LOCKFILE)
pg_basebackup: could not connect to server: FATAL:  no pg_hba.conf entry
for replication connection from host "xx.xx.xx.xx", user
"apigee", SSL off
Error: setup.sh: /appdata/apigee/apigee-service/bin/apigee-service exited with
unexpected status 1

I see an old message for recovering -

https://community.apigee.com/questions/36577/postgres-base-backup-replication-from-master-to-st.html

Another message was unanswered -

https://community.apigee.com/questions/54575/fatal-no-pg-hbaconf-node-5-of-5-node-system.html

Is that still the best course of recovery? We can set up PostgresSQL for replication as per PostgresSQL guides but what else would be needed to ensure Apigee configuration is complete?

2

BTW, there are sufficient instructions to setup PG master/slave. But, do folks consistently experience this issue?