Tilt: Docs for Minikube + local registry (was: Allow tilt to copy image from host)

[DblK]

Hi,

I do not know if tilt should do it or not (I let you decide), but due to my connexion I have an issue at first start of a cluster.
Sometime I delete my minikube cluster, and after creating a new one, the first launch is slow due to pulling all images.
I am wondering if we could have a new command to allow to copy a local image into the cluster so even if I delete the cluster I can copy/paste images and then run tilt up it will drastically increase the first launch.

What are your thoughts about it?

[victorwuky]

Hi @DblK : can you talk about why you need to delete your minikube cluster? Is it getting too slow? Or some other reason?

[victorwuky]

@nicks : Is it a good idea to have a local copy of images on the file system and push it to the cluster? Perhaps an extension candidate?

[nicks]

Hi @DblK ! This is a good question! And a common one.

If you want to copy images into a cluster, you need an in-cluster image registry. Different types of clusters have different levels of support for this. Our guide to choosing clusters has more details:

https://docs.tilt.dev/choosing_clusters.html

It's generally pretty easy to set up on Kind, Docker-for-Desktop, K3d, and Microk8s.

Minikube has registry support:
https://minikube.sigs.k8s.io/docs/handbook/registry/
but we haven't tested it with Tilt or written a guide for it.

Is it important to you that this works with Minikube, or are you able to try one of the other cluster types? I can write something up quick if it'd be helpful.

[BobyMCbobs]

I'm needing to working in-cluster, inside of Minikube. Using Tilt as part of the flow work be wonderful. Would appreciate docs for this! :smiley:

[nicks]

I played around with different configurations of Minikube and the local registry last week when I was researching the latest in local clusters.

I honestly think the best way to run Minikube is like:

minikube --driver=docker --container-runtime=containerd

and then set up a local registry running outside the cluster, but connected to the cluster network (as in our KIND example https://github.com/tilt-dev/kind-local)

There just tend to be fewer footguns where you have to configure credentials correctly, or accidentally blow away your docker cache. Want to set up a repo to document this approach, since it's a bit tricky to patch the containerd runtime