📄️ Myth: kube-proxy assign IP address to Pods
A common belief among Kubernetes users is that kube-proxy is responsible for assigning IP addresses to pods. After all, it manages networking rules and enables communication between services—so it must be the component handling pod IPs, right?
📄️ Myth: ClusterIP Service is Only for Internal Traffic
You’ve just configured a ClusterIP service to expose one of your pods internally in your Kubernetes cluster. It seems like a straightforward setup—after all, ClusterIP services are meant to route traffic between pods within the cluster, right? So, you assume that it’s all about internal communication.
📄️ Myth: ClusterIP Service Always Use Round-Robin Load Balancing
Have you ever assumed that your pods are getting equal traffic? Many engineers believe Kubernetes distributes traffic evenly across pods in a strict round-robin manner. But if you actually monitor request distribution, you’ll notice something surprising—some pods receive more traffic than others. Is Kubernetes failing at load balancing? Not really. It turns out that the default behavior isn't what most people expect.
📄️ Myth: 'kubectl port-forward svc' sends traffic to a service
Many engineers assume that running:
📄️ Myth: NodePort Service Always Exposes the Application to the Internet
During a production debugging call, a team raised an urgent security concern:
