Skip to content
Snippets Groups Projects
Commit 52f60fe7 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis
Browse files

Redirect Omnibus 15 changes to GitLab

parent 920f0923
No related branches found
No related tags found
3 merge requests!114heptapod#1394: making 1.0 the oldstable,!110heptapod#1352: merged heptapod branch into heptapod-stable,!106Merged upstream 16.4 branching point into heptapod branch
......@@ -2,5 +2,7 @@
stage: Systems
group: Distribution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
remove_date: '2024-08-21'
redirect_to: 'https://docs.gitlab.com/ee/update/versions/gitlab_15_changes.html'
---
......@@ -5,66 +7,4 @@
---
# GitLab 15 specific changes **(FREE SELF)**
NOTE:
When upgrading to a new major version, remember to first [check for background migrations](https://docs.gitlab.com/ee/update/index.html#check-for-background-migrations-before-upgrading).
## 15.11
### PostgreSQL 13 upgrade
In GitLab 15.11, PostgreSQL will automatically be upgraded to 13.x except for the following cases:
- You are running the database in high availability using Patroni.
- Your database nodes are part of GitLab Geo configuration.
- You have specifically [opted out](../settings/database.md#opt-out-of-automatic-postgresql-upgrades).
- You have `postgresql['version'] = 12` in your `gitlab.rb`
Fault-tolerant and Geo installations support manual upgrades to PostgreSQL 13, see [Packaged PostgreSQL deployed in an HA/Geo Cluster](../settings/database.md#packaged-postgresql-deployed-in-an-hageo-cluster).
## 15.6
### PostgreSQL version updates
In GitLab 15.6, the [PostgreSQL versions shipped with `omnibus-gitlab` packages](https://docs.gitlab.com/ee/administration/package_information/postgresql_versions.html)
have been upgraded to 12.12 and 13.8. Unless
[explicitly opted out](../settings/database.md#automatic-restart-when-the-postgresql-version-changes),
this can cause an automatic restart of the PostgreSQL service, and can
potentially cause downtime.
## 15.0
### PostgreSQL version updates
In GitLab 15.0, Linux package installations [ship with PostgreSQL versions](https://docs.gitlab.com/ee/administration/package_information/postgresql_versions.html) 12.10 for upgrades and 13.6 for fresh installs.
Because of underlying structural changes, the running PostgreSQL
process **_must_** be restarted when it is upgraded before running database migrations. If automatic
restart is skipped, you must run the following command before
migrations are run:
```shell
# If using PostgreSQL
sudo gitlab-ctl restart postgresql
# If using Patroni for Database replication
sudo gitlab-ctl restart patroni
```
If PostgreSQL is not restarted, you might face
[errors related to loading libraries](../settings/database.md#could-not-load-library-plpgsqlso).
### Automatic restart of PostgreSQL service on version change
Starting with GitLab 15.0, `postgresql` and `geo-postgresql` services are
automatically restarted when the PostgreSQL version changes. Restarting
PostgreSQL services causes downtime due to the temporary unavailability of the
database for operations. While this restart is mandatory for proper functioning
of the Database services, you might want more control over when the PostgreSQL
is restarted. For that purpose, you can choose to skip the automatic restarts as
part of `gitlab-ctl reconfigure` and manually restart the services.
To skip automatic restarts as part of GitLab 15.0 upgrade, perform the following
steps before the upgrade:
1. Edit `/etc/gitlab/gitlab.rb` and add the following line:
This document was moved to [another location](https://docs.gitlab.com/ee/update/versions/gitlab_15_changes.html).
......@@ -70,69 +10,5 @@
```ruby
# For PostgreSQL/Patroni
postgresql['auto_restart_on_version_change'] = false
# For Geo PostgreSQL
geo_postgresql['auto_restart_on_version_change'] = false
```
1. Reconfigure GitLab:
```shell
sudo gitlab-ctl reconfigure
```
NOTE:
It is mandatory to restart PostgreSQL when underlying version changes, to avoid
errors like the [one related to loading necessary libraries](../settings/database.md#could-not-load-library-plpgsqlso)
that can cause downtime. So, if you skip the automatic restarts using the above
method, ensure that you restart the services manually before upgrading to GitLab
15.0.
### AES256-GCM-SHA384 SSL cipher no longer allowed by default by NGINX
Starting with GitLab 15.0, the `AES256-GCM-SHA384` SSL cipher will not be allowed by
NGINX by default. If you require this cipher (for example, if you use
[AWS's Classic Load Balancer](https://docs.aws.amazon.com/en_en/elasticloadbalancing/latest/classic/elb-ssl-security-policy.html#ssl-ciphers)),
you can add the cipher back to the allow list by following the steps below:
1. Edit `/etc/gitlab/gitlab.rb` and add the following line to it:
```ruby
nginx['ssl_ciphers'] = "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:AES256-GCM-SHA384"
```
1. Run `sudo gitlab-ctl reconfigure`.
### Removing support for Gitaly's internal socket path
In GitLab 14.10, Gitaly introduced a new directory that holds all runtime data Gitaly requires to operate correctly. This
new directory replaces the old internal socket directory, and consequentially the usage of `gitaly['internal_socket_dir']`
was deprecated in favor of `gitaly['runtime_dir']`.
The old `gitaly['internal_socket_dir']` configuration was removed in this release.
### PostgreSQL 13.6 support
PostgreSQL 13.6 is being shipped as the default version for fresh installs.
Users can manually upgrade to 13.6 following the [upgrade docs](../settings/database.md#gitlab-150-and-later).
### Removed background uploads settings for object storage
Object storage now preferentially uses direct uploads.
The following keys are no longer supported in `gitlab.rb`:
- `gitlab_rails['artifacts_object_store_direct_upload']`
- `gitlab_rails['artifacts_object_store_background_upload']`
- `gitlab_rails['external_diffs_object_store_direct_upload']`
- `gitlab_rails['external_diffs_object_store_background_upload']`
- `gitlab_rails['lfs_object_store_direct_upload']`
- `gitlab_rails['lfs_object_store_background_upload']`
- `gitlab_rails['uploads_object_store_direct_upload']`
- `gitlab_rails['uploads_object_store_background_upload']`
- `gitlab_rails['packages_object_store_direct_upload']`
- `gitlab_rails['packages_object_store_background_upload']`
- `gitlab_rails['dependency_proxy_object_store_direct_upload']`
- `gitlab_rails['dependency_proxy_object_store_background_upload']`
<!-- This redirect file can be deleted after 2024-08-21. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment