Configure unique database endpoints for sidekiq and non-sidekiq servers
On GitLab.com we have different pgboucners for sidekiq and the frontend. This was done in production to deal with pgbouncer saturation, as we migrate to GitLab CNG we will need to be able to configure our sidekiq pods to use a different endpoint and database name for sidekiq.
psql: database: gitlabhq_production_sidekiq host: pgbouncer-sidekiq.int.gstg.gitlab.net port: 6432
psql: database: gitlabhq_production host: pgbouncer.int.gstg.gitlab.net port: 6432
Because the postgres settings are global we are unable to enable both sidekiq and web/api with the same chart.
Probably the best option would be to use a sidekiq value if it is set, otherwise default to the global database settings.