<p>Is it normal that I can access a pod through any worker node IP and also through master node IP?</p>
<p><code>kubectl get pods -o wide</code> shows that the pod is on one specific worker node but I can access it from any master or woker public IP. I have 1 replica of that pod.</p>
<p>Can someone help explain why?</p>

aboudirawas
<p>This is only possible if you are using NodePort type service. It's because by design the NodePort is opened on all nodes in the cluster including master nodes.</p>
<p>From the <a href="https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types" rel="nofollow noreferrer">docs</a></p>
<p><strong>NodePort</strong>: Exposes the Service on <em>each Node's IP</em> at a static port (the NodePort). A ClusterIP Service, to which the NodePort Service routes, is automatically created. You'll be able to contact the NodePort Service, from outside the cluster, by requesting <code>&lt;NodeIP&gt;:&lt;NodePort&gt;</code></p>
<p>If you are looking for a way to avoid this use <a href="https://kubernetes.io/docs/concepts/services-networking/ingress/" rel="nofollow noreferrer">ingress</a> with <code>ClusterIP</code> type service.</p>
