Skip to content

Remove Geo external DB as a limitation.

Joshua Lambert requested to merge jl-remove-geo-limitation into master

What does this MR do?

This MR removes Geo as a limitation. We don't recommend the built-in database for production, so therefore it's not really surprising we wouldn't recommend or support running Geo nodes on it either.

We should rephrase this as a Requirement for Geo, rather than a limitation. It is in fact already status as such: https://docs.gitlab.com/charts/advanced/geo/

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for omnibus-gitlab opened

Merge request reports