GitLab 11.11 arrives with instance-level Kubernetes cluster configuration

May is almost gone but the latest GitLab release just arrived!

This month’s theme is the ‘everyone can contribute’ motto and comes with support for multiple assignees for a merge request.

What’s more, in GitLab 11.11 we see a lot of container enhancements including reduced overhead with Windows support of Docker containers and provisioning instance-level Kubernetes clusters.

Let’s have a look at the most interesting highlights of GitLab 11.11.

All the highlights

Windows container executor for GitLab Runner – Allows for more advanced kinds of pipeline orchestration and management for our users of Microsoft platforms.

Caching dependency proxy for container registry – Improves execution performance for commonly used images in your environment.

Multiple assignees for merge requests – Merge requests allow multiple assignees so that all people who are responsible for the change can be assigned to merge request.

Instance-level Kubernetes cluster configuration – Self-managed users are now able to provision a cluster at the instance level, enabling all groups and projects in the instance to make use of it for its deployments.

Serialized commit graphs to improve performance – Significantly improves the speed of these traversals for large repositories. The commit graph will automatically be generated next time garbage collection is run on your repository.

SEE ALSO: Elastic Cloud on Kubernetes: Automating Elasticsearch and Kibana on Kubernetes

But that is not all! There is a big list of other improvements also featured in GitLab 11.11.

Most notably:

• Add-on CI Runner minutes have been extended to Free plans
• Access deployment details through Environments API
• Negative variable matching for pipeline rules
• API endpoint for vulnerability information
• Install Prometheus on Group-level clusters
• Full dynamic scans are now an option for DAST
• Add basic support for group GraphQL queries

There are also some important deprecations coming up that you should keep in mind:

• GitLab Geo will enforce Hashed Storage in GitLab 12.0 – Removal date: Jun. 22, 2019
• GitLab Geo will enforce using PG FDW in GitLab 12.0 – Removal date: Jun. 22, 2019
• Sentry settings for error reporting and logging will be removed from the UI in GitLab 12.0 – Removal date: Jun. 22, 2019
• Deprecate legacy code paths in GitLab Runner – Removal date: Jun. 22, 2019
  
• Git 2.21.0 or greater required – Removal date: May 22, 2019

You can find all the relevant information on the new features as well as deprecations here.

The post GitLab 11.11 arrives with instance-level Kubernetes cluster configuration appeared first on JAXenter.