18 articles tagged with Networking.
Track down what owns a busy port, decide whether to kill it or rebind, and stop TIME_WAIT from blocking your restart.
A pod can't reach a service by name, the app throws connection errors, and everyone blames the network. Usually it's DNS, and usually it's fixable.
Your pods are running, your Service exists, and nothing can reach it. Here's the exact order we check things when a Kubernetes Service goes dark.
A 502 from your ingress means no healthy backend to talk to. A 504 means the backend answered too slowly. Here's how to tell them apart and fix each.
A request leaving a laptop somehow lands on a server 20ms away. Here is what actually decides which point of presence answers.
Egress is the line item nobody sizes upfront and everyone regrets at month-end. Here's the taxonomy, the surprise bills, and what actually cuts it.
A shared API key between two internal services proves nothing about who is calling. mTLS makes every service present a cryptographic identity instead.
You run docker run, and it refuses to bind port 8080. Something already owns that port. Here is how to find the holder and get your container up.
Our failover config looked perfect in the console and did nothing during a real outage. Here's the health-check design that actually flipped regions when it mattered.
We moved 40 services off the nginx Ingress controller onto Gateway API without a single dropped connection. Here's the routing overlap trick that made it boring.
A single NAT Gateway quietly billed us $2,900 in one month, mostly for data processing on traffic that never needed to leave the VPC. Here's how we found it and cut it.
We had 140 engineers with 300 static public keys scattered across authorized_keys files nobody could audit. Moving to SSH certificates with short TTLs made access reviewable again.
