ℹ The GitLab Environment Toolkit is a collection of opinionated Terraform and Ansible scripts to assist with the deployment of a self managed GitLab environment. It's recommended that users review the Before You Start section before use. Users should have a good working knowledge of Infrastructure management, Terraform, Ansible and GitLab administration as well as be aware that ultimately self managed environments are the responsibility of the user. As such, it's strongly recommended that you independently review the Toolkit in full 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
- Added GCP VPC Network Peering support with the ability to create the peer and associated firewall rule. !1332
- Added ability to set the value for
max_unavailablefor AWS EKS node groups. !1342 (thanks@troblot!) - Introduced variable for trusted CIDR addresses for Geo Tracking Database. !1335 (thanks
@yushao.sqpc!) - Rails SSL configuration is updated to work with a custom Load Balancer outside of Ansible inventory. !1345
- Updated
kube-prometheus-stackCRDs deployment process for the setup of the monitoring stack. !1339
Upgrade Notes
Single Node GitLab environment
- MR: !1345
The following Ansible variable has been added for supporting a Single Node environment of GitLab without a separate Load Balancer:
-
gitlab_single_node_without_lb- Should be set totruewhen deploying a single GitLab Rails node without an external Load Balancer. Default isfalse.
The new variable was added to preserve previous behaviour for inventories where Load balancer was configured outside of The GitLab Environment Toolkit.
Feedback
Got any feedback or found an issue? Please feel free to create an issue on our tracker!