GitLab Wants to Be Your Only Secrets Manager
TL;DR: GitLab's Secrets Manager now works with Terraform and Kubernetes via the External Secrets Operator. This lets teams stop managing separate secret stores, simplifying workflows and boosting security by having one central place for all credentials.
Key facts
- Category
- Infrastructure
- Impact
- High
- Published
- Source
- GitLab Blog
Full summary
GitLab's Secrets Manager now supports Terraform and Kubernetes, aiming to centralize all your credentials and simplify secure development workflows.
GitLab has significantly expanded its secrets management capabilities, aiming to become a central hub for credentials across the entire software development lifecycle. According to a recent company blog post, the GitLab Secrets Manager now natively supports integrations with Terraform and the Kubernetes External Secrets Operator (ESO). This move extends its functionality far beyond its original scope of CI/CD pipelines, allowing teams to use GitLab as a single source of truth for secrets used in infrastructure provisioning and application runtime environments. The platform's secrets management engine is powered by OpenBao, an open-source fork of the popular HashiCorp Vault project, signaling a commitment to a robust and community-trusted foundation for handling sensitive data like API keys, database passwords, and certificates.
The core problem this update solves is “secrets sprawl,” a common challenge in modern DevOps environments. Teams often end up using different systems to manage secrets for different stages of development: one tool for injecting secrets into build pipelines, another for provisioning infrastructure with tools like Terraform, and yet another for providing credentials to applications running in Kubernetes. This fragmentation creates operational overhead, makes auditing difficult, and increases the risk of security gaps due to inconsistent access policies. With the new integrations, GitLab provides a unified solution. The Terraform provider allows infrastructure-as-code scripts to fetch secrets directly from a GitLab project, while the External Secrets Operator integration enables Kubernetes clusters to automatically sync secrets from GitLab and make them available to running applications in a secure, native way.
This enhancement is most impactful for developers, DevOps engineers, and security teams. For developers and DevOps practitioners, it streamlines workflows by eliminating the need to learn and manage multiple secret stores. They can now manage application code, CI/CD pipelines, and the secrets for both in a single, familiar platform. This reduces context switching and simplifies the process of securely deploying and running applications. For security teams, centralization is a major victory. It provides a single, auditable trail for all secret access across the entire lifecycle, from development to production. This makes it far easier to enforce consistent security policies, manage credential rotation, and quickly respond to potential security incidents by having a clear view of where every secret is stored and used.
The strategic implications for GitLab and the broader cloud infrastructure market are significant. By embedding comprehensive secrets management directly into its platform, GitLab is strengthening its all-in-one DevOps platform value proposition. This move positions it as a direct competitor to specialized secrets management solutions like HashiCorp Vault, AWS Secrets Manager, and Google Secret Manager. For businesses, adopting GitLab's integrated solution could lead to tangible benefits, including reduced licensing costs from consolidating tools and a lower operational risk profile. A simplified, more secure secrets management process directly translates to a stronger security posture, mitigating the chances of a costly data breach caused by a leaked or mismanaged credential.
Looking ahead, this integration lays the groundwork for GitLab to build even more sophisticated security features into its platform. We can expect to see further expansions to support other popular infrastructure tools and cloud providers. The industry-wide trend of “shifting security left”—embedding security practices earlier in the development process—is perfectly encapsulated by this update. As developers are given more responsibility for security, providing them with integrated, easy-to-use tools is critical. GitLab is betting that a unified platform is the most effective way to achieve this, and the competition in the DevOps and security tooling space will likely intensify as a result of this comprehensive approach.
Why it matters
This simplifies life for developers and security teams by replacing multiple secret stores with a single source of truth. It reduces complexity, strengthens security, and streamlines workflows across the entire software lifecycle.
Business impact
GitLab is challenging specialized tools like HashiCorp Vault, making its own platform stickier and more comprehensive. For companies, this can lead to lower costs, reduced operational risk, and faster, more secure development cycles.
Tags
Related on Notifire
Related stories
Primary source: GitLab Blog
