CloudNativeCon + KubeCon 2016

Kubernetes assumes that pods can communicate with other pods, regardless of which host they land on. Every pod has its own IP address and there’s no need to explicitly create links between pods. Mapping container ports to host ports is unnecessary.
This is an elegant design where pods can be treated much like VMs or physical hosts from the perspectives of port allocation, naming, service discovery, load balancing, application configuration and migration.

A group of people passionate about this topic from several leading and respected technology companies got together recently to form a Special Interest Group (SIG) to design the specification. The same companies that collaborated on the spec also compete on the implementation as long as they follow the following fundamental requirements (barring any intentional network segmentation policies):

• All containers can communicate with all other containers without NAT;
• All nodes can communicate with all containers (and vice-versa) without NAT;
• The IP that a container sees itself as is the same IP that others see it as.

Open source is a truly fascinating new world where people working for complementary and/or competing technologies can work together and accomplish a common goal.
This is the case of the Kubernetes Networking Special Interest Group (Kubernetes-networking-sig). The group banded together to help solve the following four networking problems:

1. Highly-coupled container-to-container communications;
2. Pod-to-Pod communications;
3. Pod-to-Service communications;
4. External-to-internal communications.

Hear from a panel ranging from open source networking projects, such as MidoNet, Contiv Calico, and Flannel, who implemented their networking for Kubernetes and get their unique perspectives on how their respective solutions augment native Kubernetes networking. With the opportunity to collaborate during the SIG and compete on the execution - this is a panel you don’t want to miss!