<p><a href="https://www.tutorialworks.com/kubernetes-imagepullbackoff/" rel="nofollow noreferrer">Re: ImagePullBackOff</a> errors: K8s &quot;relies on the fact that images described in a Pod manifest are available across every machine in the cluster&quot; ... and if that assumption is not met you might see ImagePullBackOff.</p>
<p>Just so I am totally clear here (my K8s cluster runs containerd) are these true?</p>
<ul>
<li>Once a new image is created, is the correct procedure to install it <em>to each node in the k8s cluster individually</em>?</li>
<li>Is that something the Terraform K8s provider can do? As far as I understand it, Terraform <strong>apply</strong> typically assumes the image is already known to containerd, because something else placed the images onto each node in the k8s cluster already. Terraform <strong>doesn't make the image nor does</strong> terraform place or stage images in containerd for ultimate K8s deploy. Terraform assumes that's already done.</li>
</ul>
<p>Originally I was thinking one just gives the image to the master K8s node, and then before/during deployment, K8s automagically replicates and installs it everywhere.</p>

recepient recepient
<p>The normal approach is that your images are coming from a registry that is reachable from all nodes, either a public one like Docker Hub or GitHub Packages or a private one hosted locally (sometimes even inside the cluster).</p>
<p>Technically you <em>could</em> skip that and manually distribute images to nodes some other way (for example there are some preseeding tools that use BitTorrent for it) but those are generally extremely advanced use cases. Use a normal registry :)</p>
