WIP: Geo: add secondary before db replication
What does this MR do?
Update documentation to add secondary geo node before db replication to prevent the secondary thinking its a primary.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Once the db is replicated to the secondary, the secondary doesn't realize it's not primary resulting in errors in the logs which make debugging harder.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together