Skip to content

Draft: Support non Omnibus databases with CNG Geo deployments

Ben Prescott_ requested to merge docs-bprescott/20230330-externaldb into master

What does this MR do?

A customer wants to set up Geo with cloud-native GitLab, bit use their cloud provider's database offering.

We only document how to do this with Omnibus database servers. Since we do document how to do this for Linux package deployments of the GitLab application ... the gap must be relatively narrow.

There are some gaps though - see the comment threads 1 2 3

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
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

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
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.
Edited by Ben Prescott_

Merge request reports