Telepresence 2.30.0 is out, and it changes something that has been true since the 2.x architecture was born: to receive a workload's traffic, Telepresence had to modify the workload. The new node-agent removes that requirement. You can now intercept, wiretap, replace, or ingest a workload whose pods are exactly as their owners deployed them — no sidecar injection, no pod restarts, no changes for an admission controller to argue with.
Telepresence 2.29.0 is now available. The headline change makes local
development feel local again: when one intercept handler talks to another
intercepted service, the traffic no longer takes a round trip out to the
cluster and back. This release also brings Telepresence and service meshes
much closer together — Istio ServiceEntry hosts now resolve from your
workstation, and an injected traffic-agent no longer lets application traffic
slip past the mesh.
Plenty more landed too: ingress URLs in intercept output, a consistent
--format flag for structured output, a way to expose the agent-injector
webhook to clusters whose control plane can't reach it (EKS with Calico), and a
batch of networking, IPv6/dual-stack, and Helm improvements.
Telepresence 2.28.0 is now available. This release makes it easier to work
across multiple mapped namespaces from a single connection, tightens routing
behavior for also-proxy and never-proxy, and improves several root daemon,
traffic-agent, and reconnect paths that matter in long-running development
sessions.
Telepresence 2.27.0 eliminates the need for elevated privileges during everyday use. The root daemon -- responsible for managing virtual network interfaces and DNS on your workstation -- now runs as a system service that starts automatically at boot. Once installed, telepresence connect just works, no sudo, no password prompts, no UAC dialogs.
We’re excited to announce Telepresence 2.26.0, a release focused on stronger cluster administration controls, improved intercept management in shared environments, and significant reliability and performance improvements across the Traffic Manager and Traffic Agent.
This release continues our work to make Telepresence easier to operate at scale—especially in teams where many developers share the same cluster—while also improving the day-to-day developer experience.
In the fast-paced world of Kubernetes development, efficiency and collaboration are key. That's why we're thrilled about the latest enhancements in Telepresence 2.25.0, particularly the introduction of HTTP-filtered intercepts. This powerful feature allows developers to intercept specific HTTP traffic based on headers and paths, enabling targeted debugging without hijacking an entire service. Even better, it now seamlessly integrates with TLS and mTLS-encrypted applications, making it easier to work with secure environments. In this post, we'll dive into how these features work, why they're game-changers, and how you can get started.
Discover the latest in Telepresence 2.24 with new Docker Compose extensions, seamlessly bridging local development with Kubernetes clusters. Learn how to proxy remote services, replace cluster containers with local code, and enhance your workflow using our demo. Dive into the how-to guide and reference docs to get started!
Telepresence 2.23 delivers key enhancements, including the new telepresence wiretap command for mirroring container
traffic to your client and a dedicated network driver plugin for Docker that eliminates the need for client containers
to modify their network model.
Telepresence 2.22 introduces several compelling features, notably the telepresence replace command, a JSON schema for Helm chart values, greater control over Traffic Manager's namespace scope, and improved customization of remote mount behavior.
Telepresence 2.21.0 has been released, and here is a walkthrough of its many new features, such as automatic VPN
conflict avoidance, the new telepresence ingest command, and the improved docker support provided by commands like
telepresence curl and telepresence docker-run.