Telepresence
Develop and test locally using intercepted traffic from a remote Kubernetes cluster
Best-in-class Kubernetes native development tool
What is an Intercept?
Telepresence enables precise control over traffic routing within Kubernetes clusters. It allows you to intercept traffic and redirect it to a local development environment or specific services for testing purposes. By seamlessly integrating with Kubernetes, Telepresence enables real-time interaction with running services while preserving the original network and service discovery.
What is a Personal Intercept?
Personal intercepts enable you to define conditions for when a remote request should be routed to their local container. The conditions could be anything from only routing requests that include a specific HTTP header, to requests targeting a specific route or path of an API. So you can easily intercept or selectively reroute remote traffic to the service on their local machine, and test (and share with stakeholders) how their current changes look and interact with remote dependencies–all without impacting other developers and production.
How Telepresence Works
With Telepresence, Kubernetes developers code normally, with existing tools and workflows, as though their laptops are in their Kubernetes clusters. Telepresence runs code locally and forwards requests to and from the remote Kubernetes cluster, bypassing the much slower process of waiting for a container to build, be pushed to a registry, and deployed before seeing the impact of code changes.