Tilt: Your Local Dev Loop, Now on Kubernetes

If you’ve ever spent a good chunk of your day running docker build, kubectl apply, and kubectl logs in a loop, you know the pain. You make a change, wait for the container to rebuild, push it to a registry, update the deployment, and then check if it worked. That’s not a dev loop, that’s a waiting game.

Tilt changes that. It watches your code, rebuilds automatically, and pushes updates straight into your running Kubernetes pods. No manual CI steps, no registry hopping, no wasted time.

What It Does

Tilt is a tool for local Kubernetes development. It sits in your terminal, watches your source files, and when you save a change it:

1. Detects what changed (Go, TypeScript, Python, whatever)
2. Rebuilds your Docker image (if needed)
3. Updates the running pod in your cluster
4. Streams logs back to your terminal

You don’t deploy to production through Tilt. It’s purely a local dev tool. You configure it with a simple Tiltfile (written in Starlark, a Python-like DSL) that tells it what services to build, how to build them, and where to deploy them in your cluster.

Why It’s Cool

Live updates without Docker restarts
If you’re using a language with a fast runtime (like Node, Python, or Go with air), Tilt can do resource sync. It copies changed files directly into the running container and restarts the process, not the whole container. For Go, it can even hot-reload if you set up a file watcher inside the container.

Unified dashboard
Tilt gives you a web UI at localhost:10350 where you can see all your services, their build status, log streams, and even trigger manual rebuilds. It’s like having kubectl get pods and kubectl logs in one view, but with timestamps and color.

Works with your existing setup
You don’t have to change your Dockerfiles or Kubernetes manifests. Tilt just needs to know what to build and deploy. It supports docker-compose files, raw YAML, Helm charts, and even plain Docker images.

No cluster? No problem
You can run Tilt with kind or minikube locally. It’s great for teams who share a dev cluster but want fast iteration.

How to Try It

Installing Tilt is a one-liner:

# On macOS/Linux
curl -fsSL https://raw.githubusercontent.com/tilt-dev/tilt/master/scripts/install.sh | bash

# Or via Homebrew
brew install tilt-dev/tap/tilt

Then, in your project directory, create a simple Tiltfile:

# Tiltfile
docker_build('my-service', '.')
k8s_yaml('deployment.yaml')

Run:

tilt up

That’s it. Tilt will start building, deploying, and watching. Press Ctrl+C to stop.

For a quick demo, check out their official example or run through their getting started guide.

Final Thoughts

Tilt isn’t a replacement for CI/CD. It’s a tool that makes the local dev side of Kubernetes feel like normal local development. If you’ve ever been frustrated by the slow “edit, build, push, deploy, check logs” loop, Tilt is worth a try.

It’s not perfect for everything (if you’re doing deep infrastructure changes, you’ll still want kubectl), but for day-to-day coding on a Kubernetes app, it removes a lot of friction.

Give it a spin. You might save yourself a few minutes per change — and that adds up fast.

Follow @githubprojects for more developer tools and open source projects.