DEV Community

Cover image for Develop Kubernetes Services Locally (Yes, Really) with Telepresence
Afu Tse (Chainiz)
Afu Tse (Chainiz)

Posted on

Develop Kubernetes Services Locally (Yes, Really) with Telepresence

🚀 What is Telepresence?

Telepresenceis a development tool that lets you connect your local machine directly to a Kubernetes cluster — as if your app were running inside the cluster, even though it’s actually running on your laptop.

🔥 Build, run, and debug Kubernetes services locally, without rebuilding Docker images or redeploying on every change.


🧩 What do developers use Telepresence for?

Telepresence shines in day-to-day Kubernetes development:

✅ Local development against a real cluster
• Your application runs locally
• But it consumes real cluster resources:
• Services
• ConfigMaps
• Secrets
• Internal APIs

No mocks. No fakes. Just real infrastructure.

✅ Intercepting Service traffic
• Telepresence can intercept traffic destined for a Kubernetes Service
• That traffic is transparently redirected to your local app

From the cluster’s point of view, nothing changes.

✅ Fast, comfortable debugging
• Use local logs
• Attach debuggers (VS Code, IntelliJ, etc.)
• Hot reload
• Breakpoints

🙌 All without modifying or risking remote or production environments.


😖 The problem Telepresence solves

❌ Traditional Kubernetes workflow

Every tiny change usually means:

  1. Modify code
  2. docker build
  3. docker push
  4. kubectl apply
  5. Wait for rollout
  6. Test
  7. Repeat 😵‍💫

That’s minutes per iteration — and it kills productivity.


✅ With Telepresence

The workflow becomes:

  1. Change code locally
  2. Save
  3. Test instantly

⏱️ Feedback in seconds, not minutes.


⚙️ How does Telepresence work?

flow

High-level flow:
• Connects to your Kubernetes cluster
• Deploys a Traffic Manager (proxy)
• Intercepts traffic for a Service
• Forwards that traffic to your local machine

From Kubernetes’ perspective:

👉 Your app still exists in the cluster — it just happens to live on your local machine.


🧪 Simple example

Without Telepresence

echo Service → Pod in Kubernetes
Enter fullscreen mode Exit fullscreen mode

With Telepresence

echo Service → your laptop (localhost:9000)
Enter fullscreen mode Exit fullscreen mode

Everything else stays the same:
• Databases
• Other microservices
• Secrets

🔗 Source code: github


🌟 Why you should care

• ⚡ Much faster development cycles
• 🧪 Real debugging against real infrastructure
• 🛡️ Lower risk (no touching prod clusters)
• 🧩 Perfect fit for Kubernetes & microservices

If you work with Kubernetes daily, Telepresence can seriously change how fast — and how comfortably — you build software.

--

🔗 References

Top comments (0)