[!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
- Fix ZDU post-deployment migrations failing with external Postgres. !1868
- Fix container registry metadata database configuration on multi-node Postgres setups. !1866
- Fix single-node Geo registry metadata database configuration. !1867 (thanks
@nwestbury!)
- Add
s3:GetObjectTaggingands3:PutObjectTaggingto S3 IAM policies to fix object copy failures when objects have tags - see Upgrade Notes. !1858 (thanks@eugene-park!)
Upgrade Notes
S3 IAM policy update (AWS only)
Running Terraform after upgrading will update the gitlab_s3_policy IAM policy to add s3:GetObjectTagging and s3:PutObjectTagging permissions. This is an additive change and no further action is required. These permissions are needed when objects are tagged by an external process (e.g. AWS GuardDuty) before GitLab copies them, which would otherwise cause an intermittent AccessDenied error.
Feedback
Got any feedback or found an issue? Please feel free to create an issue on our tracker!