Overlay Networking
It would be nice if all the containers across the cluster were addressable with their own IP address and we didn’t have to deal with dynamic ports or port conflicts. Kubernetes even requires each pod to have its own IP address, which is assigned from a range of IPs on the node the pod is placed. We still need some service discovery mechanism to know what IP address the service instance is at, but we don’t have to worry about port conflicts on the hosts. In some environments, it’s not possible to assign enough IP addresses to a host, and we need to manage the assignment of the IP address ranges in the environment.
We can create an overlay network on top of the existing infrastructure network that can route requests between ...
Get Microservices with Docker on Microsoft Azure™ (includes Content Update Program) 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.
