Engineering Owner: @toon ### Summary (for the Release Post; describes potential future state) Geo nodes can be deployed in different configurations. Depending on the configuration Geo upgrades require different steps. This epic contains the necessary investigations to understand *why* the documentation is written as it is, adjust the documentation where needed and add new documentation for HA Geo. ### Problem to solve Upgrading Geo is complicated and highly-manual. The documentation needs to be up-to-date, tested and should allow users to update with confidence. This epic contains work to investigate the current update procedure, update the documentation where needed, test it and add new documentation for Geo HA ### Proposal - Clean up the documentation for Geo upgrades and clearly describe steps for - Regular Geo deployment - HA deployment - HA deployment with zero downtime upgrades ### Intended users * [Sydney, Systems Administrator](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> Updates are required to: https://docs.gitlab.com/ee/administration/geo/replication/updating_the_geo_nodes.html and https://docs.gitlab.com/omnibus/update/#geo-deployment Overall, the documentation needs to be improved for HA deployments and HA + Zero downtime employments. ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> All updated documentation steps need to be tested manually and independently. ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> - Documentation for all common Geo deployments is correct, tested, up to date and available. ### What is the type of buyer? - Premium, Ultimate ### Links / references