kops/dns-controller at b1702d749e96cc0869b37bfd825e417cf809994c - kops

History

Justin Santa Barbara 31394aedfa dns-controller: include namespace in keys Avoids collisions when two services are named the same (for example). Fix #1788		2017-02-15 23:58:25 -05:00
..
cmd/dns-controller	dns-controller: include namespace in keys	2017-02-15 23:58:25 -05:00
docs	Configure dns-controller with ID of hosted zones	2016-10-06 13:12:27 -04:00
pkg	dns-controller: include namespace in keys	2017-02-15 23:58:25 -05:00
README.md	Update dns-controller README	2016-12-01 15:06:02 +05:30

README.md

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.