blob: 83f99fc2dbd07b7365736f07bc12b63cda5e0d7e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
- title: "Running a single database is deprecated"
removal_milestone: "17.0"
announcement_milestone: "16.1"
breaking_change: true
reporter: lohrc
stage: data_stores
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/411239
body: |
From GitLab 17.0, we will require a [separate database for CI features](https://gitlab.com/groups/gitlab-org/-/epics/7509).
We recommend running both databases on the same Postgres instance(s) due to ease of management for most deployments.
We are providing this as an informational advance notice but we do not recommend taking action yet.
We will have another update communicated (as well as the deprecation note) when we recommend admins to start the migration process.
This change provides additional scalability for the largest of GitLab instances, like GitLab.com.
This change applies to all installation methods: Omnibus GitLab, GitLab Helm chart, GitLab Operator, GitLab Docker images, and installation from source.
Before upgrading to GitLab 17.0, please ensure you have [migrated](https://docs.gitlab.com/ee/administration/postgresql/multiple_databases.html) to two databases.
|
