GoDaddy's kubernetes-external-secrets was the popular kid; six rivals merged into a from-scratch Go rewrite that became the de facto way secrets enter Kubernetes.

Every platform team eventually writes the same controller: one that reads a reference from Git, fetches the actual value from AWS Secrets Manager or Vault, and materializes a native Kubernetes Secret. The reason that controller has a name everyone agrees on is a story about consolidation — seven competing projects, one deliberate rewrite, and a governance stress test that arrived exactly when the project became too important to fail. This is the tale of External Secrets Operator (ESO), and of the GoDaddy project that preceded — and outlived itself into — it.

The Origin: GoDaddy's Node.js Controller and the Land Rush It Triggered

The story starts at GoDaddy in December 2018. On December 10, 2018, Jacopo Daeli pushed the initial commit to kubernetes-external-secrets (KES). It was a Node.js controller — a detail that matters enormously later. KES extended Kubernetes with an ExternalSecret CRD whose controller talked to cloud secret managers and wrote native Secrets. GoDaddy published the design motivation on its engineering blog in April 2019, and the project hit the front of Hacker News the same day with 69 points.

KES was the right idea at the right moment. Secrets in Git were anathema; secrets in clusters were already there and unrotated. By early 2021 it counted roughly 1,700 stars and supported Alibaba Cloud, Azure Key Vault, GCP, IBM Cloud, AWS Secrets Manager, AWS SSM, and HashiCorp Vault. It was, in the words of the community that would eventually replace it, "the most popular kid in school."

And that popularity created the problem. A problem this broadly felt produces a land rush: by 2020 there were at least seven projects doing the same thing — ContainerSolutions/externalsecret-operator (Go, by Riccardo M. Cefala, born from a client engagement), itscontained/secret-manager (Kellin McAvoy and Nicholas St. Germain), mumoshu/aws-secret-operator (Yusuke Kuoka), cmattoon/aws-ssm, tuenti/secrets-manager, kubernetes-sigs/k8s-gsm-tools, and GoDaddy's KES. The very first consolidation signal was prosaic: KES issue #47, "Consider merging with aws-secret-operator", filed in April 2019 by max-lobur. The merge did not happen for another eighteen months — but the idea that this problem needed one project, not seven, was now on the record.

The technical case for consolidation was written by Moritz Johner in issue #477, "Standardize CRD Spec" (September 2020): a shared CRD specification, maintained in a dedicated crd-spec repository (created November 19, 2020), so that the control plane and the ecosystem of tools around it could stabilize independently of any single implementation. The strategic case was simpler: KES was JavaScript, and the Kubernetes operator ecosystem had standardized on Go — first-class client-go SDKs, kubebuilder scaffolding, and the controller-runtime patterns every contributor already knew.

The Timeline: Consolidation, Rewrite, Crisis, Recovery

  • 2018-12-10 — Jacopo Daeli pushes the first commit to godaddy/kubernetes-external-secrets. A Node.js controller with an ExternalSecret CRD — right idea, wrong language for the ecosystem that would grow around it.
  • 2019-04-16 — GoDaddy's engineering post and a 69-point HN thread put external secret syncing on the industry's to-do list. Issue #47 proposes merging with a rival — the first consolidation signal.
  • 2020-09-01 — Moritz Johner files issue #477: Standardize CRD Spec. The community starts designing a shared CRD — the artifact that would become the point of agreement between all seven projects.
  • 2020-11-17 — The external-secrets/external-secrets repository is created, and issue #554 announces KES's move out of the GoDaddy org into the vendor-neutral external-secrets org. The rewrite is from scratch in Go on kubebuilder — no candidate repo wins as the base; only the CRD spec survives from the negotiation.
  • 2021-05-05 — First tagged ESO release: v0.1.0. The day before, Lucas Severo Alves publishes "The Birth of the External Secrets Community" — the merge story's primary account, naming all seven projects and the decision to start from scratch.
  • 2021-11-02 — KES is formally deprecated: issue #864, "KES is deprecated, migrate to ESO!". The GoDaddy project that started everything is now a migration source, with a dedicated kes-to-eso migration repo to help users across.
  • 2022-04-05 — v0.5.0 ships the architecture ESO is known for: SecretStore and ClusterSecretStore split from ExternalSecret — authentication config decoupled from data references, with a breaking dataFrom change to force the point. Fifteen months post-first-release, the API gets its adult shape.
  • 2022-08-16 — ESO is accepted into the CNCF Sandbox, entry visible on the CNCF Landscape. The consolidation project now has vendor-neutral governance to match its vendor-neutral org.
  • 2023-03-16 — v0.8.0: generators (Vault dynamic secrets), deletion policies, Keeper Security and Scaleway providers. The provider surface explodes toward the forty-odd integrations ESO lists today.
  • 2023-06-22 — v0.9.0 merges PR #2308: an explicit ESO threat model — the project starts documenting its own attack surface, a maturity marker few operators reach.
  • 2024-06-10 — The org creates bitwarden-sdk-server, a Rust SDK REST wrapper built so ESO can talk to Bitwarden Secrets Manager — evidence that the provider surface now drives dedicated infrastructure repos, not just YAML.
  • 2024-08-23 — External Secrets Inc. launches — a company (maintainer Gusfcarvalho among its principals) selling an enterprise distribution around the project, with the externalsecrets.com commercial site framing ESO as a "credential transport layer for non-human identity." Open-core economics arrive.
  • 2025-08 — The burnout test. Maintainers announce a pause on new releases until more maintainers step up (HN, 2025-08-13). External Secrets Inc. publishes "ESO at a Turning Point", committing upstream investment and framing its enterprise product as the funded path. The five-year-old project is too widely deployed to stall quietly.
  • 2025-11-07 — Recovery ships: v1.0.0 GA. Four and a half years after the first tagged release, ESO declares its API stable — a deliberate, almost glacial path to 1.0 that few CNCF projects match.
  • 2026-02-06 — v2.0.0 removes the unmaintained Alibaba and Device42 providers — the first breaking-cleanup release, and proof the project can now shed dead weight faster than it once shipped features.
  • 2026-09-18 — v2.11.0: Barbican application-credential auth, webhook GetAllSecrets semantics, Keeper fixes. Eleven days before this article, the cadence that nearly stalled in 2025 is back to roughly monthly.

Crisis Points and Architectural Pivots

The consolidation itself was the first crisis, and it was engineered rather than survived. Seven projects with overlapping CRDs is a fragmentation tax on the entire ecosystem: every blog post, every helm chart, every platform template had to pick a winner. The external-secrets community solved it with process — a negotiated common CRD spec first, implementation second — and then did the counterintuitive thing: rather than adopting the codebase of the largest candidate, they rewrote from scratch and "just copied and adapted code that made sense." The CRD was the point of agreement; the code was disposable. That decision is why ESO's API feels designed rather than accreted.

The SecretStore split (v0.5.0) was the architectural pivot that made ESO deployable at scale. The original single-resource design coupled where a secret lives with how to authenticate to that backend. v0.5.0 pulled authentication into namespaced SecretStore and cluster-wide ClusterSecretStore resources, letting platform teams own store definitions once while application teams emitted only ExternalSecret references. It forced a breaking change on dataFrom to get there. This is the split that turns ESO from a syncing tool into platform plumbing — the reason an internal developer platform can offer "secrets" as a service with one ClusterSecretStore per backend.

apiVersion: external-secrets.io/v1
kind: SecretStore          # namespaced: how to authenticate
metadata:
  name: vault-prod
spec:
  provider:
    vault:
      server: "https://vault.example.com"
      path: "secret"
      auth:
        kubernetes:
          mountPath: "kubernetes"
          role: "eso"

---
apiVersion: external-secrets.io/v1
kind: ExternalSecret      # what to fetch, by reference
metadata:
  name: payments-api-key
spec:
  refreshInterval: 1h
  secretStoreRef:
    name: vault-prod
    kind: SecretStore
  target:
    name: payments-api-key
  data:
    - secretKey: api-key
      remoteRef:
        key: payments/prod
        property: api-key