GitLab puts power of Kubernetes in developer workflow with extended integration

1 Mins read

GitLab is extending its integration with Kubernetes, by bringing it into the developer workflow. It will make it easier for enterprises and developers to drive innovative software to production.

A single application for the DevOps lifecycle, GitLab comes with a built-in container registry and Kubernetes integration. This makes things simple while getting started with containers and cloud-native development for optimization of app development processes.

Using GitLab, all the developers in the organization can access Kubernetes, which helps in speeding up the process of software development.

“By allowing people to quickly connect Kubernetes clusters to their projects we are helping many enterprises embrace the cloud native way of building applications,” says Sid Sijbrandij, CEO at GitLab.

“By providing a single application we allow enterprise developer and operations teams to embrace Kubernetes every step of the way in their software development process. We’ve seen a large financial institution go from a single build every two weeks to over 1,000 self-served builds a day using GitLab. It is wonderful to see the scale we can unlock for organizations by providing access to Kubernetes in the developer workflow.”

Developers will be able to connect their existing Kubernetes cluster (on any platform) to GitLab. They can also easily set up and configure new clusters using Google Kubernetes Engine (GKE) integration. After setting up the clusters, they can install managed apps like Helm Tiller, Ingres, and Prometheus to their cluster.

Integration of GitLab and Kubernetes will provide a number of advanced capabilities, like Deploy Boards, Canary Deployments, Kubernetes monitoring, Auto DevOps, and Web Terminals.

Deploy Boards will provide a unified view of the current health and status of CI/CD environments that run on Kubernetes.

GitLab will provide automatic detection and monitoring of Kubernetes clusters via the Prometheus.

Also read: Top 5 collaboration tools for DevOps teams

Further, the Auto DevOps is a default setting for CI/CD that automatically generates pipelines without any configuration. Lastly, the Interactive Web Terminals will provide instant web access to a terminal for remote environments to make troubleshooting easier.

Leave a Reply

Your email address will not be published. Required fields are marked *

ninety four − 85 =