Latest

You're troubleshooting a service outage in production. Your application logs show connection timeouts, but you can't see what's actually happening on the network. Traditional tcpdump would require SSHing into a container, installing binaries you don't have permission to change, or restarting your pod with a privileged sidecar. By the time you've navigated those hurdles, the issue has either disappeared or your debugging window has closed.

This is the reality of network troubleshooting in Kubernetes. The tools exist, but they feel fundamentally at odds with how containers and orchestration work.

What if you could capture network traffic—complete with Kubernetes context—without touching a single container? What if you could do it from your laptop in Wireshark, watching live traffic stream in, each packet tagged with its pod name, namespace, and container? That's no longer hypothetical. Inspektor Gadget's tcpdump gadget, released in v0.45.0, makes this possible using eBPF—and a new Wireshark integration brings it all together seamlessly.