diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-19 15:57:54 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-19 15:57:54 +0300 |
commit | 419c53ec62de6e97a517abd5fdd4cbde3a942a34 (patch) | |
tree | 1f43a548b46bca8a5fb8fe0c31cef1883d49c5b6 /doc/administration/geo/disaster_recovery/index.md | |
parent | 1da20d9135b3ad9e75e65b028bffc921aaf8deb7 (diff) |
Add latest changes from gitlab-org/gitlab@16-5-stable-eev16.5.0-rc42
Diffstat (limited to 'doc/administration/geo/disaster_recovery/index.md')
-rw-r--r-- | doc/administration/geo/disaster_recovery/index.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/administration/geo/disaster_recovery/index.md b/doc/administration/geo/disaster_recovery/index.md index 0c160e85570..d6f6211ed4c 100644 --- a/doc/administration/geo/disaster_recovery/index.md +++ b/doc/administration/geo/disaster_recovery/index.md @@ -670,7 +670,9 @@ If the secondary site [has been paused](../../geo/index.md#pausing-and-resuming- a point-in-time recovery to the last known state. Data that was created on the primary while the secondary was paused is lost. -If you are running GitLab 14.5 and later: +::Tabs + +:::TabTitle For GitLab 14.5 and later 1. For each node (such as PostgreSQL or Gitaly) outside of the **secondary** Kubernetes cluster using the Linux package, SSH into the node and run one of the following commands: @@ -706,7 +708,7 @@ If you are running GitLab 14.5 and later: | ---- | ------------- | ------- | | `ENABLE_SILENT_MODE` | `false` | If `true`, enables [Silent Mode](../../silent_mode/index.md) before promotion (GitLab 16.4 and later) | -If you are running GitLab 14.4 and earlier: +:::TabTitle For GitLab 14.4 and earlier 1. SSH in to the database node in the **secondary** site and trigger PostgreSQL to promote to read-write: @@ -744,6 +746,8 @@ If you are running GitLab 14.4 and earlier: kubectl --namespace gitlab exec -ti gitlab-geo-task-runner-XXX -- gitlab-rake geo:set_secondary_as_primary ``` +::EndTabs + ### Step 3. Promote the **secondary** cluster 1. Update the existing cluster configuration. |