Command Palette

Search for a command to run...

Hectal
Phase 6Advanced7 of 8 in Networking

Troubleshooting & Container Networking

A repeatable debugging method and toolkit, reading packet captures of your own traffic, how containers get networks (namespaces, veth, bridges), and how Kubernetes CNIs and eBPF move pod traffic.

The final phase turns everything into practice: a method for 'it can't connect' problems, tools for each layer, and a look under the hood of Docker and Kubernetes networking, so that pod-to-pod traffic, Services, and NetworkPolicies are just the routing, NAT, and bridges you already understand.

0/3 · 0%
3 topics ~23 min 5 code blocks & diagrams
Start with the first topic
1
6.1

A Method for 'It Can't Connect'

Work from the bottom layer up, change one thing at a time, and use one command per question: name resolution, route, reachability, port, then application.

7 min 1 code practice

2
6.2

How Containers Get a Network: Namespaces, veth & Bridges

A container's network is a Linux network namespace connected to the host through a veth pair plugged into a bridge, with NAT for outbound traffic and DNAT for published ports.

8 min 1 diagram 1 code practice

3
6.3

Kubernetes Networking: CNI, kube-proxy & eBPF

Kubernetes requires every pod to reach every other pod without NAT; a CNI plugin implements that across nodes, kube-proxy (or eBPF) implements Services, and NetworkPolicies filter it.

8 min 1 diagram 1 code practice