Communication flow from Pod 3 to Pod 6

Lets look at the communication flow from Pod3 to Pod6 which is housed in single node:

1. A packet leaves from Pod 3 through the eth3 interface and reaches the cbr0 bridge interface through the veth1234 virtual interface.
2. The packet leaves veth1234 and reaches cbr0, looking for the address of Pod 6.
3. The packet leaves cbr0 and is redirected to veth5678.
4. The packet leaves cbr0 through veth5678 and reaches the Pod 6 network through the eth6 interface.

On a regular basis, Kubernetes destroys and rebuilds Pods. As a result, Services that have a stable IP address and enable load balancing among a set of Pods must be used. The kube-proxy component residing in the node takes care of communication between Pods and Services.

The flow of traffic from a client Pod 3 to a server Pod 6 on a separate node is depicted in the following diagram. The Kubernetes application programming interface (API) server keeps track of the application...