Hacker News Reader

Kubernetes pod networking really depends on the networking plugin and cloud platform. For example on AWS VPC-CNI, pods are directly attached to a network interface (on the VPC level) and directly get an IP from that — no NAT. These network interfaces don't show up on the host OS.

View on HN

Yeah; this article seems like a pretty nice overview of how Linux network namespaces work, but my frustrations usually aren't at that level. I usually know what I want in those terms, but it seems like the container runtimes/frameworks often refuse to do it for obscure reasons, or it requires knowledge of undocumented implications.

Well, more or less. The pod IPs are assigned to the host ENIs and not to pods directly. The VPC CNI manages the virtual Ethernet devices in the host and pod network namespaces and sets up routes on the host such that inbound traffic using a pod IP will get routed to the correct virtual Ethernet device for the corresponding pod.

Reply on news.ycombinator.com