So far, our discussion has focused on a single-node Docker networking environment. While single-node Docker networking is feature-rich with network isolation and DNS, it is all still contained within a single host. This means traffic between containers doesn't have to hit an external network. Additionally, it means our platform is restricted to a single node, limiting our ability to scale and failover. So, now we extend our focus to clusters running containers with both Swarm and Kubernetes orchestrators. This means that our containers need to not only communicate with other containers on the same node, but they also need to span the network and communicate with containers running on different ...
Introduction to cluster-based container networking
Get Mastering Docker Enterprise now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.