[!important]
The GitLab Environment Toolkit automates deploying and managing scaled GitLab environments following the Reference Architectures. It's recommended that users review the Before You Start section before use. Users are expected to have a good working knowledge of Terraform, Ansible, GitLab administration, and infrastructure management, as environments ultimately remain the responsibility of the user. As such, it's strongly recommended that you independently review the Toolkit in full before any use to ensure it meets your requirements, especially around security or data integrity.
If upgrading, it's always recommended to review the release notes in full as well as the relevant documentation and to upgrade the Toolkit first before the environment.
Changes
- Enabled
pg_stat_statementsextension across all database setups, including Cloud Native deployments. !1844
- Fixed SSL/TLS certificate configuration for Cloud Native deployments using Envoy Gateway, including correct TLS termination mode, consistent certificate structure across all web services, and disabling certificate management when ingress is disabled. !1846 (thanks
@nwestbury!)
- Fixed database extension being installed in the wrong database for Cloud Native Helm Chart deployments. !1848 (thanks
@Frogvall!)
- Fixed Geo Zero Downtime Upgrade post-deployment migrations conditional and renamed
gitlab_charts_zero_downtime_geo_post_deployment_migrationstogeo_zero_downtime_run_post_deployment_migrations. !1849 (thanks@nwestbury!)
- Suppressed verbose Envoy Gateway CRD output in Ansible runs to prevent exceeding CI log limits. !1851 (thanks
@dat.tang.gitlab!)
Upgrade Notes
Geo ZDU post-deployment migrations variable renamed
The gitlab_charts_zero_downtime_geo_post_deployment_migrations operational flag introduced in 3.10.0 has been renamed to geo_zero_downtime_run_post_deployment_migrations to better reflect that it applies to both Omnibus and Helm Chart Geo deployments. If you used this flag during a Zero Downtime Upgrade in 3.10.0, update the variable name accordingly for future runs.
Feedback
Got any feedback or found an issue? Please feel free to create an issue on our tracker!