Docs - Promote Geo secondary nodes on external PostgreSQL databases
What does this MR do?
Our documentation includes instructions on how to perform a Geo failover for single nodes and HA. It does not have anything for Geo nodes that have an external PostgreSQL database ie. RDS or Azure. We haven't tested this personally, but we are confident that these instructions will work.
Refer to Slack thread in #g_geo (internal use only) for more information.
This documentation was written to support this customer in a ticket - ZD (internal use only), who I will ask to provide us with feedback on how the instructions go for them.
Tested failover instructions on DB type
-
Non-bundled PostgreSQL server (installed via PPA) -
AWS RDS -
Azure -
GCP
Related issues
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖