One of the strong features of the kubernetes provided by docker desktop is the same image cache as the docker engine itself.
As result the docker image created localy by docker build is available immediately in the kubernetes.
We don’t need to push the image to the registry and pull it again in the kubernetes
it saves lot of time
explained here https://www.docker.com/blog/how-kubernetes-works-under-the-hood-with-docker-desktop/
However I see that this feature works only in the kuberneted created by kubeadm
If I select the option to create the kubernetes by kind , it doesn’t work. The image is unavailable and need to push it somehow to the kuberentes cache.
Do I miss something ?Are any plans to fix it somehow ?
Here is my guess. The single node cluster created by kubeadm had to work with a single node so the single image cache was fine, but with kind, you can run multiple nodes and you cannot use a single docker data root with its only image cache for multiple nodes. So I assume when kind runs its containers, each container will have its own data including its own image cache.
I’m not sure my guess is right, but that behavior would be understandable. I also understand your expectation, so if you could ask for a feature in the roadmap
It would need to be properly designed, but I guess (yes, again) some features could be developed for kind in Docker Desktop to automatically import locally built images to each node, but that would also increase the used space on the disk, so it should be optional.
So while a new feature could be introduced, I don’t think you could use the single instance of the image you built with docker commands.