Skip to content

Geo: add configuration for role and tracking database

Jason Plum requested to merge 1212-geo-add-configuration into master

Geo: Add geo-logcursor chart v1

Add a chart under gitlab/ as geo-logcursor.

This chart makes use of gitlab-geo-logcursor CNG container from gitlab-org/build/CNG!220 (merged)

The chart requires the addition of templates to configure the related tracking database, as well as enable/disable of related components.

NOTICE: This change does not include database seeding, migrations for global.geo.psql database, which is currently assumed to pre-exist, and be up to date on migrations, per the used container.

TODO:

  • Add configuration to all Rails containers
    • Unicorn
    • Sidekiq
    • Task-Runner
  • Template geo.node_name into gitlab.yml when global.geo.nodeName is present
  • Documentation #1213 (closed), !1041 (merged)
  • CI (skipped because #1211 (closed) is not closed by CNG!220)

Closes #1212 (closed)

Important Notes

  • It was found that a manual edit of the Geo node (/admin/geo/nodes) was required in order to update the external URL of the node to gitlab-k3s.example.com when originally having configured geo2.example.com Omnibus as secondary. @mkozono to add this docs.gitlab.com/ee/administration documentation.
  • Further exploration of a clean setup of Geo (primary and secondary) with databases provided via the Omnibus GitLab within #1213
Edited by Jason Plum

Merge request reports