History

John Gardiner Myers 9f3e31c73b Merge branch 'master' into critical-pod Conflicts: upup/pkg/fi/cloudup/bootstrapchannelbuilder.go upup/pkg/fi/cloudup/tests/bootstrapchannelbuilder/amazonvpc/manifest.yaml upup/pkg/fi/cloudup/tests/bootstrapchannelbuilder/cilium/manifest.yaml upup/pkg/fi/cloudup/tests/bootstrapchannelbuilder/simple/manifest.yaml upup/pkg/fi/cloudup/tests/bootstrapchannelbuilder/weave/manifest.yaml		2020-01-29 09:15:56 -08:00
..
README.md	Correct link error:404	2019-11-20 14:17:26 +08:00
k8s-1.6.yaml.template	Bump feature flag version for external-dns addon.	2017-09-16 13:05:55 +02:00
k8s-1.12.yaml.template	Add missing priorityClassName for critical pods	2020-01-21 21:03:07 -08:00

README.md

ExternalDNS

ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers.

What it does

Inspired by Kubernetes DNS, Kubernetes' cluster-internal DNS server, ExternalDNS makes Kubernetes resources discoverable via public DNS servers. Like KubeDNS, it retrieves a list of resources (Services, Ingresses, etc.) from the Kubernetes API to determine a desired list of DNS records. Unlike KubeDNS, however, it's not a DNS server itself, but merely configures other DNS providers accordingly—e.g. AWS Route 53 or Google CloudDNS.

In a broader sense, ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way.

Deploying to a Cluster

The following tutorials are provided:

AWS
Azure
Cloudflare
DigitalOcean
Google Container Engine
- Using Google's Default Ingress Controller
- Using the Nginx Ingress Controller
FAQ

Github repository

Source code is managed under kubernetes-incubator at external-dns.