The Kubernetes network model makes every pod reachable from every other pod and lets every node reach every pod, regardless of the pod's node. A container can accept connections through its pod IP and bound port even when the port is omitted or incorrect in the manifest; declaring ports documents exposure and enables named service ports. section 5.3.1
Test connectivity through progressively longer paths:
- From the hosting worker node, curl the pod IP and port; local communication provides the shortest diagnostic route. section 5.3.1
- From a temporary client pod, curl the target pod to test whether normal pod-to-pod communication works. section 5.3.1
- Use kubectl port-forward for local access through a proxy, rather than testing the direct cluster network path. section 5.3.1
Testing a pod from another pod
Run `kubectl run --image=curlimages/curl -it --restart=Never --rm client-pod curl 10.244.2.4:8080`. The temporary client receives the application's response and is then deleted. section 5.3.1
$ kubectl get pod kiada -o wide NAME READY STATUS RESTARTS AGE IP NODE ... kiada 1/1 Running 0 35m 10.244.2.4 worker2 ...
Inspect a pod's IP and assigned node before testing direct connectivity. section 5.3.1
