Who’s Calling That API? A Detective Story from the Depths of EKS Networking
A production network got hammered by too many Auth0 token requests. The source? EKS workloads tucked behind a shared NAT Gateway. No easy trail. Engineers stitched it together usingVPC Flow Logs,pod-to-node maps, and some sharpIstio ServiceEntry logs. Even with Kubernetes CNI doing its NAT-obscuring..