Re:Docker Networking and DNS: The Good, the Bad, and the Ugly
by HorizonXP on Monday April 25, 2016 @03:35PM
(#11566723)
Personally, I like how Kubernetes handles this with an independent service that's built upon flannel (Kube-DNS). I'd rather Docker stick to running containers, and that's it.
[ Parent
| on HN ]
Re:Docker Networking and DNS: The Good, the Bad, and the Ugly
by jmspring on Monday April 25, 2016 @03:49PM
(#11566819)
Weave (https://github.com/weaveworks/weave) is actually a nice DNS/SDN solution for Docker. Quick and easy to set up.
Re:Docker Networking and DNS: The Good, the Bad, and the Ugly
by yissachar on Monday April 25, 2016 @04:06PM
(#11566931)
I tried Weave but ultimately had to abandon it, as there were too many issues in resolving DNS directly to containers. Kubernetes resolves DNS to a virtual IP that in turns maps to the container IPs, which I found to be a much better approach.
Re:Docker Networking and DNS: The Good, the Bad, and the Ugly
by jmspring on Monday April 25, 2016 @11:21PM
(#11569204)
My initial work with it was pre-docker networking. Admittedly, I need to spend more time with Kubernetes, but the rapid evolution and multiple solutions to service discoverability, load balancing, and networking in the Docker eco-system is a bit of a challenge to keep on top of and figure out what's best/right for the situation. I suspect, near term, the solution is "what works for me now, I'll figure out something else as I have time/down the road."