diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-04 00:09:24 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-04 00:09:24 +0300 |
| commit | 9432ed811233643af1cb5ad78e2cd9755ed989a9 (patch) | |
| tree | a6f4d254ebd818a58017b3bfb0911f4aae169fcf /doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md | |
| parent | 44434461b3c58336624125b5ab002e7200e4a208 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md')
| -rw-r--r-- | doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md | 16 |
1 files changed, 4 insertions, 12 deletions
diff --git a/doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md b/doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md index 2fc933d8ef1..b6c8e1c124f 100644 --- a/doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md +++ b/doc/architecture/blueprints/pods/proposal-stateless-router-with-routes-learning.md @@ -73,7 +73,7 @@ graph TD; end ``` -<details><summary>More detail</summary> +### More detail This shows that the router can actually send requests to any pod. The user will get the closest router to them geographically. @@ -105,9 +105,7 @@ graph TD; router_us-.->pod_eu1; ``` -</details> - -<details><summary>Even more detail</summary> +### Even more detail This shows the databases. `gitlab_users` and `gitlab_routes` exist only in the US region but are replicated to other regions. Replication does not have an @@ -160,8 +158,6 @@ graph TD; router_us-.->pod_eu1; ``` -</details> - ## Summary of changes 1. Tables related to User data (including profile settings, authentication credentials, personal access tokens) are decomposed into a `gitlab_users` schema @@ -302,7 +298,7 @@ keeping settings in sync for all pods. Handling shared `gitlab_users`, `gitlab_routes` and `gitlab_admin` databases, while having dedicated `gitlab_main` and `gitlab_ci` databases should already be handled by the way we use `config/database.yml`. We should also, already be able to handle the dedicated EU replicas while having a single US primary for `gitlab_users` and `gitlab_routes`. Below is a snippet of part of the database configuration for the Pod architecture described above. -<details><summary>Pod US0</summary> +**Pod US0**: ```yaml # config/database.yml @@ -329,9 +325,7 @@ production: discovery: postgres-admin-replicas.us.consul ``` -</details> - -<details><summary>Pod EU0</summary> +**Pod EU0**: ```yaml # config/database.yml @@ -358,8 +352,6 @@ production: discovery: postgres-admin-replicas.eu.consul ``` -</details> - ## Request flows 1. `gitlab-org` is a top level namespace and lives in `Pod US0` in the `GitLab.com Public` organization |