Same-node pod calls work, cross-node calls time out, and small probes pass while real requests hang. Find the break.

Same-node good, cross-node bad is not a random clue, it is nearly a diagnosis. One short decision tree separates overlay reachability, encapsulation blocks, MTU and policy.

Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

Same-node good, cross-node bad is not a random clue, it is nearly a diagnosis. One short decision tree separates overlay reachability, encapsulation blocks, MTU and policy.

20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25

UP NEXT ON YOUR JOURNEY

Next in this trackA rolling update stalls halfway: new replicas crash-loop and old ones are already scaled down. What are your first moves?Next in this trackAll stages green except the production deploy, which failed three runs in a row. Nobody changed anything. Where do you dig first?Next in this trackA service on a VM dies and restarts every few minutes, and the team has shrugged for weeks. Find the actual cause.

DISCUSSION · 0

Nothing here yet. Say how you would answer it.