# GitLab's Secrets Manager pushes software delivery beyond CI/CD Source: TechNewsList (https://technewslist.com) Canonical URL: https://technewslist.com/en/article/gitlab-secrets-manager-infra-control-plane-2026-08-25-night Section: Software (https://technewslist.com/en/software) Author: TechNewsList Language: en Published: 2026-08-25T17:27:25.16+00:00 Updated: 2026-08-25T17:27:25.333406+00:00 > GitLab's new Secrets Manager support for ESO, Terraform, and API access turns secret storage into a broader software control plane for app and infrastructure workflows. ## TL;DR - GitLab added ESO, Terraform, and API support to its Secrets Manager. - The feature extends secret retrieval beyond CI/CD jobs into Kubernetes and infra-as-code workflows. - It makes secrets management feel more like an application control plane than a narrow dev tool. ## Key points - GitLab is pushing secret management deeper into the rest of the software stack. - The update matters because modern software teams now run more than CI jobs. - The API and Terraform support make the product more useful for automation-heavy infrastructure teams. - OpenBao and Vault-compatible thinking make the release easier to understand for security teams. - The broader software market is moving toward policy-aware building blocks instead of isolated tools. ## What happened GitLab has expanded Secrets Manager with support for External Secrets Operator, Terraform, and direct API access. That sounds like a narrow product update, but it actually changes the scope of where GitLab can sit in a software organization. ![Contextual editorial image for GitLab's Secrets Manager pushes software delivery beyond CI/CD GitLab Secrets Manager External Secrets Operator Terraform OpenBao GitLab Blog GitLab Docs Investing.com technology news](https://miro.medium.com/v2/resize:fit:1358/1*grxi0YJvhV8EgiUNGL8kFQ.png) *Contextual visual selected for this TechPulse story.* Instead of being useful only inside CI/CD, the product now reaches into Kubernetes workloads, infrastructure-as-code pipelines, and other non-CI/CD systems that need controlled access to secrets. That makes the feature feel more like a general control layer for software operations. ## Why it matters Software teams do not live in one tool anymore. They live in a mesh of app code, infrastructure code, identity systems, and automated deployment steps. Secret management becomes painful when each of those layers needs its own credential workflow. GitLab's update matters because it tries to remove that fragmentation. If one secrets store can serve CI jobs, Terraform runs, and external workloads, teams spend less time duplicating policy and more time enforcing it consistently. That also makes the product more attractive to larger organizations, where security review is a recurring bottleneck. A feature that reduces credential sprawl and makes permissions more portable is more valuable than another isolated developer convenience. It also fits the broader direction of software tooling in 2026. The best platforms are not just where code lives. They are where policy, access, and audit evidence live too. The more a tool can absorb those responsibilities, the less reason teams have to stitch together multiple vendors. ## Technical details The implementation is built around OpenBao and a Vault-compatible KV v2 API. That is important because it means GitLab is not inventing a weird proprietary secret format. It is leaning into a model security teams already understand. ![Contextual editorial image for GitLab's Secrets Manager pushes software delivery beyond CI/CD GitLab Secrets Manager External Secrets Operator Terraform OpenBao GitLab Blog GitLab Docs Investing.com technology news](https://insight.infograb.net/img/blog/2026-06-24-gitlab-secret-manager.863ccfa8.webp) *Contextual visual selected for this TechPulse story.* The new API access also means non-CI/CD workloads can pull secrets directly without going through a runner job. That helps with Kubernetes apps, infrastructure automation, and other systems that need credentials outside the classic pipeline flow. The result is a cleaner software delivery chain. GitLab stores and manages the secret, Terraform or another external tool requests it through the API, and policy remains visible rather than hiding in ad hoc scripts. The practical payoff is that software teams can standardize secret retrieval across build, deploy, and runtime contexts. That reduces the chance that a one-off script becomes a permanent security blind spot. It also makes it easier to rotate credentials and audit where they are actually consumed. ## Market / industry impact The bigger market story is that software platforms are becoming control planes, not just code hosts. Customers want one place to manage code, policy, secrets, deployment, and audit evidence. GitLab keeps pushing in that direction. The more it can centralize security-sensitive workflows, the more it can compete on operational trust instead of just repository hosting. That is a better long-term position in a market where AI-driven software delivery is increasing the number of machines acting on behalf of humans. It also puts pressure on point solutions. Secret managers, infrastructure tools, and CI vendors all have to prove why they deserve a separate purchase if GitLab can now cover more of the stack. The message to buyers is equally clear: if your software stack is getting more automated, your secret management probably needs to become more programmable. GitLab is trying to own that part of the stack before someone else turns it into a separate platform category. ## What to watch next Watch adoption in real infrastructure-heavy teams, especially those using Terraform and Kubernetes at scale. Watch whether the beta grows into a standard part of GitLab's paid tiers. And watch whether other software platforms respond by broadening their own secrets stories. If they do, that will confirm the direction of travel: the best software delivery tools are becoming the systems where teams enforce trust, not just where they store code. The next milestone is adoption, not announcement. If teams start replacing scattered secret workflows with this model, GitLab's move will look less like a feature update and more like a platform consolidation play. ## Sources - [GitLab Blog](https://about.gitlab.com/blog/gitlab-secrets-manager-add-eso-terraform-api-support/) - Official release announcement. - [GitLab Docs](https://docs.gitlab.com/ci/secrets/secrets_manager/non_cicd_access/) - Documentation for non-CI/CD access. - [Investing.com](https://www.investing.com/news/company-news/gitlab-releases-version-193-with-ai-gateway-and-secrets-manager-93CH-4870506) - Secondary coverage of GitLab 19.3 and Secrets Manager. Mentions: GitLab, Secrets Manager, External Secrets Operator, Terraform, OpenBao, CI/CD, Kubernetes ## Sources - [GitLab Blog](https://about.gitlab.com/blog/gitlab-secrets-manager-add-eso-terraform-api-support/) - [GitLab Docs](https://docs.gitlab.com/ci/secrets/secrets_manager/non_cicd_access/) - [Investing.com](https://www.investing.com/news/company-news/gitlab-releases-version-193-with-ai-gateway-and-secrets-manager-93CH-4870506)