Debug intermittent pod-to-pod connectivity
WHAT IT TESTS: systematic network debugging. OUTLINE: scope the failure by path, rule out DNS, inspect kube-proxy iptables and conntrack, check the CNI, then verify cloud security groups and MTU. RED FLAG: restarting pods with no hypothesis.
WHAT IT TESTS: whether you debug a flaky network methodically from L3 up. ANSWER OUTLINE: reproduce and scope it (same node vs cross-node, intermittent vs total), rule out DNS with dig, check kube-proxy iptables or IPVS rules and the conntrack table for races, inspect the CNI for IP exhaustion or overlay issues, and examine cloud security groups, route tables and MTU, since overlay headers can drop large packets. RED FLAG: restarting components blindly or ignoring conntrack and MTU.
Read the original → interview
- #kubernetes
- #networking
- #cni
- #debugging
- #troubleshooting
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.