pulling from a private registry

A couple notes on auth:

• Tilt will use the registry auth mechanism of your underlying image build tool. So if you use docker_build, Tilt will use the auth credentials of your Docker service. So you don't need to worry about auth when you push the image.

• In MOST environments (Minikube, Docker for Mac, Kind, K3d, Microk8s), Tilt will do as much as it can to deploy your images directly to the cluster (rather than a remote registry). In these cases, you don't need to worry about auth when you pull the image

But in environments where you pull the image from a private registry, you need to setup the cluster with the auth credentials for that registry. Here's a doc on how to do that:

https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

I don't have a good sense of how common this is, or if it's worth trying to make it a better experience. Where "make this a better experience" can be anything from:

• Linking to that doc when you get image pull auth errors
• Automatically injecting image pull secrets when Tilt deploys things
• Doing more to help you configure an in-cluster registry (like we do with Kind/K3d/Microk8s)

Leaving this ticket open mostly to collect thumbs-up for people interested in this, or comments on what might be helpful

Start with the Kubernetes documentation on pulling images from a private registry and review the existing behavior for Docker builds and cluster image deployment. No repository files or tests are named, and the issue does not define a single completion condition; possible outcomes include linking auth errors, injecting image pull secrets, or improving in-cluster registry setup.