<p>I am deploying docker containers on a kubernetes cluster with 2 nodes. The docker containers need to have port 50052 open. My understanding was that I just need to define a containerPort (50052) and have a service that points to this.</p>
<p>But when I deploy this, only the first 2 pods will spin up successfully. After that, I get the following message, presumably because the new pods are trying top open port 50052, which is already being used.</p>
<blockquote>
<p>0/2 nodes are available: 2 node(s) didn't have free ports for the requested pod ports.</p>
</blockquote>
<p>I thought that multiple pods with the same requested port could be scheduled on the same node? Or is this not right?</p>

jrdzha
<p>Thanks, I figured it out -- I had set host network to true in my kubernetes deployment. Changing this back to false fixed my issue.</p>
