GitLab 13.11 Announced to Scale DevOps with Kubernetes Agent and Pipeline Compliance
GitLab 13.11 is now Live. Last week, on Earth Day (22 April), open DevOps platform GitLab announced GitLab Kubernetes Agent and Compliant Pipeline Configurations. With these new updates, GitLab 13.11 is scaling DevOps practices with automated control and efficiencies.
Here’s a quick overview of GitLab 13.11.
Recommended: Global Edtech Major UpGrad Raises USD 120 Million
GitLab Kubernetes Agent
GitLab Kubernetes Agent is the foundation block of GitLab’s Kubernetes integrations. It will integrate your pull-based deployments with GitLab’s server-side components. GitLab 13.11 is expected to add push-based deployments too in the near future.
In recent months, GitLab has made tremendous progress in its Kubernetes deployment offerings. Kubernetes, an open-source container orchestration platform now ties in with GitLab’s core to enable customers to respond quickly to containerization and virtualization demands. For micro-service-oriented Cloud and App-native systems, Kubernetes + GitLab is an agile DevOps option.
This is what GitLab offers with its Kubernetes integration:
- GitLab CI/CD pipelines to deploy container software
- Use Kubernetes to manage runners attached to any GitLab instance
- GitLab application and services for any Kubernetes cluster
GitLab Kubernetes Agentill further simplifies running GitLab instances on the Kubernetes cluster with the help of GitLab CI/CD and GitLab Runners.
You can now manually test changes in a live, faster production-simulated environment before merging code with Review Apps.
Read More: Atlassian Acquires ThinkTilt, Maker Of ProForma, To Further Augment Jira
Compliant Pipeline Configurations
Compliant Pipeline Configurations is automated monitoring, tracking and controlling feature that can keep your automation on track as you grow and scale with Kubernetes workflow. It works in tandem with GitLab 13.11 Custom Compliance Framework Labels to help you define enforceable security structures and requirements beyond PCI, HIPPA and so on.
With the help of Compliant Pipeline Configurations, users can eliminate the manual steps required for pipeline configuration in every Kubernetes project. It also prevents the need to manually edit and remove errors and noise. Security and Compliance teams can focus on monitoring core Devops processes to extend and modify custom detection rules, a popular request from GitLab SAST customers.
Read Also: Vectra Expands Integration Ecosystem to Provide 100% Visibility and Automated Response
[To share your insights on CI / CD pipelines, DevOps and Kubernetes, please write to us at sghosh@martechseries.com]
Comments are closed.