Skip to content

Docs: Merge EE doc/administration/high_availability to CE

Marcel Amirault requested to merge (removed):docs-repo-merge-8-admin-ha into master

What does this MR do?

Ported to EE in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12107.

This aligns the CE and EE doc/administration/high_availability docs, as part of the effort to combine docs into a single codebase (&199 (closed))

This MR:

  • Brings in EE only files:
    • administration/high_availability/alpha_database.md
    • administration/high_availability/consul.md
    • administration/high_availability/gitaly.md
    • administration/high_availability/nfs_host_client_setup.md
    • administration/high_availability/pgbouncer.md
  • Brings EE only information into:
    • administration/high_availability/README.md
    • administration/high_availability/database.md (was updated in EE but never ported to CE)
    • administration/high_availability/gitlab.md (was updated in EE but never ported to CE)
    • administration/high_availability/redis.md (was updated in EE but never ported to CE)
  • Brings in 1 image related to the docs above.
  • Updates relative links to absolute, as necessary.

When both the EE Port and this MR are merged, the doc/administration/high_availability docs should hopefully be aligned between CE and EE.

Then, please merge: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12105, and the issue will be closed.

Related issues

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/60832

Author's checklist

  • Follow the Documentation Guidelines and Style Guide.
  • 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

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

Merge request reports