Starting with GitLab 10.1 you can easily connect your Google account to your projects and create a new Kubernetes cluster directly from the GitLab Cluster page. Then you can use it to host Review Apps and deployment environments.
GitLab Enterprise Edition Premium provides additional levels of control to your workflow to ensure that strict policies can be enforced within your development environment.
With Commit Author Restriction, it is now possible to ensure that the committer is the same user pushing changes back to the repository. This can prevent unauthorized code entering your codebase or enforce tightly controlled developer workflows.
You can choose to apply this setting to individual repositories, or across the entire GitLab instance to enforce server-wide control.
Used in conjunction with EEP’s ability to reject unsigned commits you can now be in complete control of identity and verification when changes are applied to your repositories in GitLab.
Many teams who use GitLab are geographically spread out, but your GitLab instance is in a single location. GitLab Geo brings GitLab closer to your team, making fetch operations like cloning repositories faster.
GitLab Geo is now generally available! When configured, GitLab Geo keeps read-only secondaries in sync with your primary GitLab instance. You can use GitLab Geo to access Git, LFS objects, issues, wikis, and CI artifacts from the closest GitLab instance.
Note: while Geo and High Availability are now each individually GA, use of GitLab Geo in combination with High Availability, is considered Beta.
Notable changes shipped with GitLab 10.2:
- Added HTTPS Git replication support
- Added secure PostgreSQL replication
- Added API to retrieve geo status
- Improved handling of replication errors
See full the list of changes for Geo on 10.2
For many organizations, GitLab is a critical component of their software engineering tool chain, powering not only their code repository but also CI/CD, issue management, and much more. To ensure GitLab is available around the clock it can be deployed in a highly available configuration, providing additional redundancy and scale.
With GitLab 10.2, we are proud to announce that PostgreSQL High Availability is now generally available. As part of GitLab Enterprise Edition Premium, the Omnibus installation package makes setting up a production Postgres database cluster easy.
In the event a database node goes down, the cluster will automatically fail over ensuring your developers flow isn’t interrupted.