Most Kubernetes origin stories start with a vendor's grand strategy. This one starts with an argument about DNS records. In 2016 the same problem had three working answers and no official one: kops had a dns-controller, Zalando had Mate, and a Boston consultancy called Molecule had route53-kubernetes. Kubernetes contributors, allergic to letting three tools solve an API-shaped problem, did the one thing open source is actually good at: they fused the three projects into one, seeded it in the incubator, and promised it would replace kops' controller by v1.0. Nine years and twenty-three releases later, ExternalDNS runs in thousands of clusters, has never shipped a 1.0, and the kops dns-controller it was going to kill is still in the tree. It is the most successful unfinished project in the Kubernetes ecosystem, and the story of why is a lesson in how Kubernetes really governs itself.

The Origin: Three Tools, One Argument, and a Repo Seeded by Hand

The pre-history: kubernetes#28525, July 2016

The paper trail starts before the repo does. On , Tim Hockin — the Google engineer who built Kubernetes' Service abstraction in the first place — opened kubernetes/kubernetes#28525, titled "Add Google Cloud DNS support to LoadBalancer Services." The issue was classic Hockin: a gap in the API surface that forced every operator to glue a DNS zone to a load balancer by hand. Six months of circular discussion later, his January 5, 2017 comment on the same thread laid down the design constraint that still defines the project: DNS is not the Service's job, so the record creation belongs in a controller watching from outside. Three tools had already reached that conclusion independently. Kubernetes had three answers and zero standards.

2016 ── THE PROBLEM STATE, per kubernetes/kubernetes#28525
        "kubectl expose" gives you an IP. DNS is someone else's problem.

  ┌─────────────────────────────┬──────────────────────────────┬─────────────────────────────┐
  │ kops dns-controller         │ Zalando Mate                 │ Molecule route53-kubernetes │
  │ (kubernetes/kops, 2016)     │ (zalando, Nov 2016)          │ (wearemolecule, Jun 2015)   │
  │ cluster bring-up records    │ Route53 + CloudDNS for       │ Route53 ALIAS for k8s       │
  │ + service/ingress records   │ services + ingresses        │ ingresses/services          │
  │ annotations: dns/           │ annotations: zalando.org/    │ annotations: domainName     │
  │                             │                              │                            │
  │ maintainer: Justin Santa    │ maintainers: Martin          │ maintainer: Adam            │
  │ Barbara (Google, kops)      │ Linkhorst, Henning Jacobs   │ Sunderland (Molecule)      │
  │                             │ (Zalando)                    │                            │
  └──────────────┬──────────────┴───────────────┬──────────────┴─────────────┬──────────────┘
                 │                              │                            │
                 └──────────────┬───────────────┴────────────────────────────┘
                                ▼
              Feb 2017: kubernetes-incubator/external-dns
              "a fusion of the following projects, driven by its maintainers"
                                │
                                ▼
              The v0.1.0 README roadmap, March 2017:
                v1.0 → "Ability to replace Kops' DNS Controller"