Draft: Clarify primary <> secondary network requirements
What does this MR do?
This MR proposes some clarification regarding the network requirements between primary and secondary clusters on a Geo Helm (Kubernetes) installation.
This stems from a Slack discussion about a certain lack of clarity in requirements: (internal, only available 90 days).
It is not clear what the supplied database is, and how the secondary and primary database and sites need to communication with each other.
The main confusion potentially comes from the implicit differences between a site (i.e an "instance" of Gitlab) and a node (i.e an individual server), as defined in the Geo glossary. This is compounded by the fact that a node is also a Kubernetes concept.
Author checklist
For general guidance, please follow our Contributing guide.
Required
For anything in this list which will not be completed, please provide a reason in the MR discussion.
-
Merge Request Title and Description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
MR has a green pipeline. -
Documentation created/updated. -
Tests added/updated, and test plan for scenarios not covered by automated tests. -
Equivalent MR/issue for omnibus-gitlab opened.
Reviewers checklist
-
MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab. -
Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab Chart.