Networking with Docker and Kubernetes is a lot more complex than with traditional servers and virtual machines. Docker uses network namespaces and virtual interfaces to isolate container networks, while Kubernetes may use iptables rules to provide service routing and is commonly deployed with an overlay network (such as Flannel) in order to support a large IP space without having to reconfigure the existing physical network. Beyond that, you can add in network policies if that isn’t confusing enough.
Jeff Poole offers an overview of the concepts involved and explains what tuning may be required to use Kubernetes successfully. Jeff also covers examples of tracing network traffic through the system and explores special considerations, such as how to determine if you need to adjust the ARP table size on your hosts.
Jeff Poole is an engineering director over a set of teams that handle both operations and software development at Vivint Smart Home, where he works on the backend platform that powers the smart home and security aspects of Vivint’s products. Over his career, he’s held a diverse collection of roles and responsibilities, including technical lead in creating a multi-data-center-hosted VoIP platform and principal engineer designing networking hardware for defense applications. An adrenaline junkie, he’s moved from skydiving to working on an ambulance and in an ER to working on production systems.
For exhibition and sponsorship opportunities, email email@example.com
For information on trade opportunities with O'Reilly conferences, email firstname.lastname@example.org
View a complete list of Velocity contacts
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com