Open ronaldpetty opened 7 years ago
I have a pretty interesting use in mind for CoreDNS and welcome opinions:
By convention, the demo uses a url of the format for discovery: masters.{clustername}.k8s, minions.{clustername}.k8s.
Right now the glue for that is a Route53 Private Hosted Zones and a Lambda on the side that listens to AutoScaling events and syncs to the Zone. It works great but obviously is not portable between clouds.
It might be possible to simplify this a bit with CoreDNS.
cc: @miekg
@johnbelamaric
By convention, the demo uses a url of the format for discovery: masters.{clustername}.k8s, minions.{clustername}.k8s.
Is this actually using k8s? Or just using these names?
Right now the glue for that is a Route53 Private Hosted Zones and a Lambda on the side that listens to AutoScaling events and syncs to the Zone. It works great but obviously is not portable between clouds.
I think I'm parsing this correctly.... If you use CoreDNS with etcd (version 2 only atm) as a backend and somehow get the AutoScaling events to update the state in etcd, this should work.
This has been open since March; is there any progress of note?
Need to update demo app to include CoreDNS usage.