@@ -164,6 +164,7 @@ New users and SSH keys updated after this step, will be replicated automatically
...
@@ -164,6 +164,7 @@ New users and SSH keys updated after this step, will be replicated automatically
in your browser.
in your browser.
1. Add the secondary node by providing its full URL and the public SSH key
1. Add the secondary node by providing its full URL and the public SSH key
you created previously. **Do NOT** check the box 'This is a primary node'.
you created previously. **Do NOT** check the box 'This is a primary node'.
1. Added in GitLab 9.5: Choose which namespaces should be replicated by the secondary node. Leave blank to replicate all. Read more in [selective replication](#selective-replication).
1. Click the **Add node** button.
1. Click the **Add node** button.
---
---
...
@@ -250,6 +251,21 @@ If your installation isn't working properly, check the
...
@@ -250,6 +251,21 @@ If your installation isn't working properly, check the
Point your users to the [after setup steps](after_setup.md).
Point your users to the [after setup steps](after_setup.md).
## Selective replication
With GitLab **9.5**, GitLab Geo now supports the first iteration of selective
replication, which allows admins to choose which namespaces should be
replicated by secondary nodes.
It is important to notice that selective replication:
1. Does not restrict permissions from secondary nodes.
1. Does not hide projects metadata from secondary nodes. Since Geo currently
relies on PostgreSQL replication, all project metadata gets replicated to
secondary nodes, but repositories that have not been selected will be empty.
1. Secondary nodes won't pull repositories that do not belong to the selected
namespaces to be replicated.
## Adding another secondary Geo node
## Adding another secondary Geo node
To add another Geo node in an already Geo configured infrastructure, just follow
To add another Geo node in an already Geo configured infrastructure, just follow
