Accelerate Inner Dev Loop
Kubernetes was supposed to make your team faster, but now everytime you make a code change you have to wait for containers to build, be pushed to registry, and deployed. With Telepresence, you can make changes to your service as if you're developing locally, without having to run all the dependencies on your local machine.
Shift Testing Left
You want to catch errors before they get shipped to production, but to do that you need a realistic development environment and with Kubernetes, those can be expensive. Telepresence lets you connect the copy of your service locally to your remote dependencies, so you can test like your laptop is in your cluster.
Use Your Existing Workflow
Missing your favorite code editor, debugger, or profiler? Anything that runs on your laptop works with Telepresence - even when you're working on a service running in Kubernetes.
How does it work?
Telepresence consists of two core architecture components: the client-side telepresence binary (CLI on your workstation) and the cluster-side traffic-manager and traffic-agent (on the remote Kubernetes cluster).
Telepresence consists of two core architecture components: the client-side (CLI) telepresence binary and (Kubernetes) cluster-side traffic-manager and traffic-agent.
The `telepresence connect` command utilizes the traffic-manager to establish a two-way (proxied) tunnel between your local development machine and the cluster. Now you can access remote K8s Service as if they were running locally.
Running `telepresence intercept service-name` triggers the traffic-manager to install a traffic-agent proxy container that runs within the Pods associated with the target Services. This can route remote traffic to your local dev machine for dev and test.
Telepresence is under active development. Subscribe to get updates and announcements:
The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.