- Summary of major changes
- Upgrade path from 5.x
- Upgrade from 5.10.x
- Major Changes
- Release cadence
- Kubernetes deployment support
- Technical support
Along with the
15.0 release of GitLab, we have bumped the chart version to
- The recommended PostgreSQL database is upgraded to 13.
- The default list of allowed ciphers for NGINX Ingress has been changed to remove weak ciphers. This might break some AWS deployments. See issue #3317 for more information.
In order to upgrade to the
6.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
5.10.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 6.0.0 (GitLab 15.0.0). It is required to upgrade to the latest 5.10.x version first before proceeding. Please follow the upgrade documentation at https://docs.gitlab.com/charts/releases/6_0.html and upgrade to GitLab Helm chart version 5.10.x before upgrading to 6.0.0.
Please follow the normal upgrade steps.
PostgreSQL 13 is the recommended version, but PostgreSQL 12.x is still supported.
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
Before opening an issue please search to see if a similar issue already exists.
We greatly appreciate the wider testing of the community, and encourage detailed issues to be reported so we can address them.