Version management: GitLab 14.1 extends the connection to Kubernetes

Share your love

One month after the last major version, GitLab has now released version 14.1 of the version control platform. The innovations are mainly to be found in the commercial versions and are aimed, among other things, at connecting to Kubernetes. Other additions such as requirements for test coverage for merge requests are aimed at quality assurance.

GitLab had already improved the connection to Kubernetes in version 13.11. Since then, the GitLab Kubernetes agent has been taking care of the pull-based distribution of software and the integration of network security requirements. Now the platform extends the integration to the CI / CD processes (Continuous Integration, Continuous Delivery) via GitLab Runners. A CI / CD tunnel takes care of their connection to the Kubernetes cluster and uses the GitLab Kubernetes agent for this. This eliminates the need to open the firewall for the cluster.

The integration of Helm charts is also aimed at the interaction with Kubernetes. Helm is a package manager for Kubernetes, and GitLab’s package registry has recently added Helm packages to packages from other package managers and formats such as npm, NuGet, PyPI, Maven and Composer. While the CI / CD tunnel is reserved for the commercial variants, helmet charts can also be created, published, shared and managed in the free variant of GitLab.

With the newly introduced escalation policies, teams determine that alerts automatically take the next escalation level if nobody at the current level addresses the problem within a predefined period of time.

The approval rule dialog allows configuration for a coverage check as a requirement for merge requests.

(Image: GitLab)

In order to keep the test coverage for projects at a sufficiently high level, teams can define a rule that requires a coverage check for a merge request. Basically, the function was already available in version 14, but with the current release it can be comprehensively configured.

The Ultimate version can now also include external status checks for merge requests, for example to check access rights. The new tab also shows Changes in GitLab Ultimate which line in the source represents a violation of the code quality. The tab summarizes the information from the diff view and the merge request page in a compact way.

Code quality violations can be shown more clearly in the current release.

(Image: GitLab)

Further innovations can be found in GitLab 14.1 in the official announcement. There you can also see which new functions are available for the Free, Premium and Ultimate variants.


(rme)

Article Source

Read Also   Core i-12000 "Alder Lake": Hybrid design for CPUs should bring Intel forward
Share your love