History

Kubernetes Submit Queue 2b2b5971b5 Merge pull request #3859 from justinsb/upsert_dns_records Automatic merge from submit-queue. Use upsert when applying DNS records		2017-11-15 08:39:38 -08:00
..
cmd/dns-controller	gazelle updates with new bazel version	2017-11-05 17:41:53 -07:00
docs	fixing up the line length	2017-06-08 11:00:33 +01:00
pkg	Merge pull request #3859 from justinsb/upsert_dns_records	2017-11-15 08:39:38 -08:00
README.md	Keeping this file <=72	2017-06-08 11:06:56 +01:00

README.md

dns-controller

dns-controller creates DNS records.

In the bring-up of a new cluster, protokube has already ensured that we have an etcd cluster and an apiserver. It also sets up DNS records for the etcd nodes (this is a much simpler problem, because we have a 1:1 mapping from an etcd node to a DNS name.)

However, none of the nodes can reach the api server to register. Nor can end-users reach the API. In future we might expose the API server as a normal service via Type=LoadBalancer or via a normal Ingress, but for now we just expose it via DNS.

The dns-controller recognizes annotations on nodes.

dns.alpha.kubernetes.io/external will set up records for accessing the resource externally
dns.alpha.kubernetes.io/internal will set up records for accessing the resource internally

When added on Service controllers:

dns.alpha.kubernetes.io/external creates a Route53 A record with public IPs of all the nodes
dns.alpha.kubernetes.io/internal creates a Route53 A record with private IPs of all the nodes

The syntax is a comma separated list of fully qualified domain names.