- Summary of major changes
- Upgrade path from 4.x
- Upgrade from 4.12.x
- Major Changes
- Upgrade path from versions prior to 4.x
- Known issues and limitations
- Release cadence
- Kubernetes deployment support
- Technical support
Along with the
14.0 release of GitLab, we have bumped the chart version to
- The bundled PostgreSQL database is upgraded to 12.7
- Dropped support for Unicorn as webserver
- No longer supporting installs using Helm 2.x
- The bundled Cert-Manager chart has been upgraded to 1.2.0
In order to upgrade to the
5.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.
If you don’t first upgrade to the latest
4.12.x patch, you will see the following error from
Error: UPGRADE FAILED: Job failed: BackoffLimitExceeded
You can then confirm you are in this situation by looking for pods in error with the text
gitlab-upgrade-check in the name.
If you check the logs for those pods will see the version upgrade error message:
It seems you are upgrading the GitLab Helm Chart from X (GitLab X) to 5.0.0 (GitLab 14.0.0). It is required to upgrade to the latest 4.12.x version first before proceeding. Please follow the upgrade documentation at https://docs.gitlab.com/charts/releases/5_0.html and upgrade to GitLab Helm Chart version 4.12.x before upgrading to 5.0.0.
Please follow the upgrade steps for 5.0 release.
As part of the
5.0.0 release of this chart, we upgraded the PostgreSQL version from
12.7. This is not a
drop in replacement. Manual steps need to be performed to upgrade the database.
The 5.0 upgrade steps includes the manual steps required during upgrade.
4.0.0 of the chart the use of Unicorn as webserver was deprecated and no longer used by default, instead
Puma has been used as the default webserver. In
5.0.0 Unicorn support has been removed.
You will need to remove any Unicorn configuration from your values before upgrading to the newest version.
For Puma configuration options see the Webservice details.
Helm 2 has been deprecated and is no longer supported upstream with its last release being in November 2020. The
release of the GitLab Helm Chart is the last to support Tiller Helm 2.x.
As part of the
5.0.0 release of this chart, we upgraded the Cert-Manager chart from
1.2.0. The new
version uses the
cert-manager.io/v1 API version for the
Issuer so if you were using a seperate Cert-Manager
instance but still using the Issuer provided by this chart, you will need to upgrade your Cert-Manager to a version
that supports the
If you are using the Cert-Manager and
Issuer provided by this chart, the upgrade should happen automatically. During
the upgrade the Cert-Manager
Deployment objects (previously named with
certmanager in their name), will be deleted,
and new ones will be created with
cert-manager in the name.
Check the Cert-Manager upgrade troubleshooting section if you run into issues with Cert-Manger during upgrade.
You first need to upgrade to the
4.12.x release of the charts, before upgrading to
4.0. Please follow the
4.0 upgrade documentation.
Below is a list of the known issues and limitations, although it may not be exhaustive.
Features that are currently out of scope:
- Relative URL as the GitLab Endpoint: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/406
We will be releasing a new version of the chart with each new GitLab patch.
More information on how we are versioning the chart can be found in the release documentation.
Along with the issues and merge requests in this repository, a changelog is available to more easily follow along with updates.
GitLab is tested against:
Other Kubernetes deployments should also work. In the event of a specific non-GKE deployment issue, please raise an issue.
This release has automated CI testing for Kubernetes version
We greatly appreciate the wider testing of the community, and encourage detailed issues to be reported so we can address them.