Telepresence

Fast, local development for Kubernetes and OpenShift Microservices

Telepresence is a

Cloud Native Computing Foundation Sandbox project initially created by the team at Ambassador

Why Telepresence?

Speed Up Your Inner Dev Loop

Kubernetes should make your team faster. But every time you make a code change, you have to wait for containers to build, be pushed to a registry and deployed. With Telepresence, you develop as if everything runs on your machine. No need to manage dependencies. Code, test, and see results immediately.

Shift Testing Left

You want to catch errors before they reach production. To do this, you need a realistic development environment. However, Kubernetes environments can be costly. Telepresence solves this by letting you connect your local service to remote dependencies. This allows you to test as if your laptop is part of the cluster.

Use Your Existing Workflow

Missing your favorite code editor, debugger, or profiler? You can use anything that runs on your laptop with Telepresence. This includes services running in Kubernetes.

Used by

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).

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.

To find out more about the Telepresence Architecture, check out the

docs or join us in the #telepresence-oss channel on the CNCF Slack.

get started