- Summary of major changes
- Upgrade path from 6.x
- Upgrade from 6.11.x
- Major Changes
Along with the
16.0 release of GitLab, we have bumped the chart version to
- The recommended PostgreSQL database is upgraded to 14.8.
- The bundled certmanager chart is upgraded from 1.5.4 to 1.11.1.
In order to upgrade to the
7.0 version of the chart, you first need to upgrade to the latest
release of the chart. Check the version mapping details for the latest patch.
GitLab now defaults to using two database connections. Prior to upgrading, you can check that PostgreSQL
high enough (using more than 50% of the available max connections).
You can verify this by running the following Rake task using the Toolbox container:
If the task indicates that
max_connections is high enough, then you can
proceed with the upgrade. If not, or you wish to remain on single
connection, you can set the
ci.enabled key to
false prior to the upgrade.
Please follow the upgrade steps for 7.0 release.
As part of the
7.0.0 release of this chart, we upgraded the default PostgreSQL version from
is done by upgrading PostgreSQL chart version from
This is not a drop in replacement. Manual steps need to be performed to upgrade the database. The steps have been documented in the upgrade steps.
The bundled certmanager chart is upgraded from 1.5.4 to 1.11.1. Depending on your cluster and tooling this may require manual interaction before upgrading.
Make sure your cluster version is supported by certmanager 1.11. The release supports Kubernetes 1.21 to 1.26 and OpenShift 4.8 to 4.13. See certmanager supported releases for more information.
The default certmanager configuration now uses the
As a result, certmanager will use the existing Ingresses to complete ACME challenges instead of creating
new ones. This change was made to ensure compatibility with Ingress controllers that need the
to be set.
OpenShift users may have to modify the Security Context Constraints to deploy certmanager 1.10+. See certmanager 1.10 release notes for more information.
In case you deploy any certmanager custom resources not managed by the GitLab chart, or use additional scripts or tooling related to cert-manager, please read through the potentially breaking changes of certmanager 1.6 to 1.11 before upgrading.
sub-chart has been updated to version
16.13.2 from the previously installed
11.3.4. This also upgrades Redis from
Manual steps are required prior to upgrading if using the bundled Redis. See Upgrade the bundled Redis sub-chart