Most Kubernetes networking problems come down to the same handful of misunderstandings, yet they are all fixable once you see how the pieces actually fit together. In this talk, we’ll start with the basics: every pod gets its own IP from a cluster-wide CIDR, so pods can talk to each other directly without NAT tricks. From there, we’ll dig into Services: ClusterIP for internal routing, NodePort for quick external access, and LoadBalancer for when you need your cloud provider to hand you a real endpoint. Then we’ll tackle the part that interests most people: getting traffic into the cluster. We will visit Ingress with the newer Gateway API. We will look at how each handles HTTP routing and TLS, and talk about why Gateway API is worth paying attention to now. You will leave with a working mental model of how traffic flows from a user’s browser all the way to your application pod.