Geo: Recommended updates after assisting customer setting up Geo
A number of issues were observed whilst assisting a customer setting up Geo, here are some recommendations for how to address:
SSH
- Update https://docs.gitlab.com/ee/administration/operations/fast_ssh_key_lookup.html#setting-up-fast-lookup-via-gitlab-shell
- To have a more step based flow, including disabling the writing of authorized_keys to be more obvious
- Include steps on how to best validate that fast SSH key lookup is working.
- Add a new setting to
/etc/gitlab/gitlab.rb
(and then agitlab-ctl reconfigure
) that enables fast SSH key lookup without needing to update/etc/ssh/sshd_config
by hand.
gitlab-ctl replicate-geo-database
- When specifying
--skip-backup
, it needs to handle if data dir is missing. - Needs to handle
postgresql.conf
being missing. - Currently confirming, but when setting
postgresql['data_dir']
to something custom in/etc/gitlab/gitlab.rb
, it appears to be ignored bygitlab-ctl replicate-geo-database
and the default/var/opt/gitlab/postgresql/data
is used.
Adding Geo nodes via the UI
- Have a more accurate and useful error message in the Geo UI when adding a secondary.
- Discern between a secondary that's misconfigured vs. a secondary that's currently in the process of being configured.
Edited by 🤖 GitLab Bot 🤖