<p>We need to scale up pods in our AKS Cluster. </p>
<p>Somethimes we need to spin up so much, that multiple extra nodes are needed. </p>
<p>Our docker image is 20GB big to pull. <br>
(Yes I know its way to big, but it's impossible to reduce the size due being an older application.) </p>
<p>But I'm wondering if we spin up 5 new pods on 1 new node, do they all 5 start pulling the 20GB image at startup? Due the image is not cached. </p>
<p>If they do, is there a way to prevent this? </p>
<p>I prefer to have 4 pods waiting for pod 1 to download the image then downloading it 5 times.</p>

<p>Images are cached on the node to speedup new created pods on the same node.</p>
<p>A very simple way to prevent that would be starting one pod per node at first and then scaling it up so the container runtime can reuse the previously pulled image.</p>
