There a few valid situations where you don’t want to follow the common deployment practice by pushing to container registry and then let Kubernetes pull it during deployment.
This is mostly the case during the software development phase where you quickly want to test your code on Kubernetes cluster local or remote, because the whole container image up and download is slow.
> A key feature of BuildKit CLI for kubectl is that it strives to make the images you build immediately available in the container runtime of your Kubernetes cluster so you can “bounce” your pod(s) to pick up a freshly built image with virtually no overhead.
This is mostly the case during the software development phase where you quickly want to test your code on Kubernetes cluster local or remote, because the whole container image up and download is slow.
> A key feature of BuildKit CLI for kubectl is that it strives to make the images you build immediately available in the container runtime of your Kubernetes cluster so you can “bounce” your pod(s) to pick up a freshly built image with virtually no overhead.