- ‣ NSA Recommends the Use of TLS 1.2 or TLS 1.3 as Other TLS Versions Prove Obsolete
- ‣ Cockroach Labs publishes the 2021 Cloud Report
- ‣ The United Nations Suffers a Data Breach, Exposing 100,000 Employee Details
- ‣ KubeSphere Extends Collaboration To Amazon Web Services
- ‣ Red Hat To Acquire StackRox and Bring More Security To OpenShift Platform
- ‣ DataStax Releases K8ssandra – The Latest Production-Ready Platform for Running Apache Cassandra on Kubernetes
- ‣ AWS Launches Location Service, Opening New Opportunities For Developers
- ‣ GDPR Violations Lead To $66,000 Fine for Swedish University
- ‣ CloudLinux To Invest A Million Dollars Annually In Project Lenix
- ‣ Google Launches Machine Query Language in General Availability for Cloud Monitoring
- ‣ AWS Launches Service Workbench for Researchers
- ‣ AWS Batch Support Now Available for AWS Fargate
- ‣ Highest-Rated Cloud Computing Companies to Work For in 2021
- ‣ Mirantis Launches k0s - The Smallest, Simplest Kubernetes Distro
- ‣ AWS Fault Injection Simulator Improves Cloud Chaos Engineering
- ‣ China claims it’s quantum computer is 100 trillion times faster than any supercomputer
- ‣ Red Hat OpenShift to Support Windows Containers from 2021
GitLab 13.4 combines CI and Vault
Sept. 27, 2020, 5:42 p.m. in DevSecOps
Topline
GitLab version 13.4 enables secrets managed in Hashicorp's Vault to be injected into the Continuous Integration (CI) process.

Key Facts
With version 13.4, GitLab extends the platform's DevSecOps capabilities with new features.
The integration of direct injection of secrets managed in the Hashicorp Vault into the Continuous Integration (CI) process.
The integration of the new GitLab Kubernets agent (GKA).
The support for automatic version control for new Terraform states files
Integration of GitLab Security Center (formerly GitLab Instance Security Dashboard) with reports and vulnerability settings.
More
GitLab 13.4 incorporates other enhancements, such as allowing deployment without code access privileges to keep development and deployment tasks separate. In other words, the Deployer role follows the least privilege access concept, enabling developers to accept merge requests and deploy code in secure environments without needing access to change the code itself. This version comes also with enhancements in UX.