Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
DOWNLOADING CONCEPT: 1. THE CNI & POD IP ADDRESSES...
↳In Docker, containers are isolated behind a NAT bridge.
↳In Kubernetes, the rule is simple: Every Pod gets its own IP address, and every Pod can talk to every other Pod across any node without NAT.
↳Who gives the Pods these IP addresses? The Container Network Interface (CNI).
↳Popular CNIs include Calico, Cilium (eBPF), and Flannel.
↳When a Pod starts, the CNI creates a veth (Virtual Ethernet) pair.
↳One end lives inside the Pod's network namespace, and the other end lives in the Node's root namespace.
↳The CNI then configures routing tables across the cluster (often using BGP or Overlay Networks like VXLAN) so that packets seamlessly jump between worker nodes.
▲ LIVE INCIDENTA service is up, pods are running, but curling the service name returns 'Connection refused'.
sre@arena:~/k8s-networking
sre@arena:~$ kubectl get endpoints backend-service