Telepresence is an open source tool that enables you to set up remote development environments for Kubernetes where you can still use all of your favorite local tools like IDEs, debuggers, and profilers.
A Kubernetes Deployment and Service.
Install Telepresence by running the relevant commands below for your OS. If you are not the administrator of your cluster, you will need administrative RBAC permissions to install and use the Telepresence traffic-manager in your cluster.
# 1. Download the latest binary (~95 MB):sudo curl -fL https://app.getambassador.io/download/tel2oss/releases/download/v2.17.1/telepresence-linux-amd64 -o /usr/local/bin/telepresence# 2. Make the binary executable:sudo chmod a+x /usr/local/bin/telepresence
# Intel Macs# 1. Download the latest binary (~105 MB):sudo curl -fL https://app.getambassador.io/download/tel2oss/releases/download/v2.17.1/telepresence-darwin-amd64 -o /usr/local/bin/telepresence# 2. Make the binary executable:sudo chmod a+x /usr/local/bin/telepresence# Apple silicon Macs# 1. Download the latest binary (~101 MB):sudo curl -fL https://app.getambassador.io/download/tel2oss/releases/download/v2.17.1/telepresence-darwin-arm64 -o /usr/local/bin/telepresence# 2. Make the binary executable:sudo chmod a+x /usr/local/bin/telepresence
Installing Telepresence on Windows is easy. Download this zip folder and run the powershell script.
- Install the traffic manager into your cluster with
telepresence helm install. More information about installing Telepresence can be found here. This will require root access on your machine.
$ telepresence helm install...Traffic Manager installed successfully
With Telepresence, you can create global intercepts that intercept all traffic going to a service in your remote cluster and route it to your local environment instead.
Connect to your cluster with
telepresence connectand connect to the Kubernetes API server:Terminal$ telepresence connectconnected to context <your-context>Terminal$ curl -ik https://kubernetes.defaultHTTP/1.1 401 UnauthorizedCache-Control: no-cache, privateContent-Type: application/json...
You now have access to your remote Kubernetes API server as if you were on the same network. You can now use any local tools to connect to any service in the cluster.
telepresence listand make sure the service you want to intercept is listed. For example:Terminal$ telepresence list...example-service: ready to intercept (traffic-agent not yet installed)...
Get the name of the port you want to intercept on your service:
kubectl get service <service name> --output yaml.
For example:Terminal$ kubectl get service example-service --output yaml...ports:- name: httpport: 80protocol: TCPtargetPort: http...
Intercept all traffic going to the service in your cluster:
telepresence intercept <service-name> --port <local-port>[:<remote-port>] --env-file <path-to-env-file>.
Terminal$ telepresence intercept example-service --port 8080:http --env-file ~/example-service-intercept.envUsing Deployment example-serviceinterceptedIntercept name: example-serviceState : ACTIVEWorkload kind : DeploymentDestination : 127.0.0.1:8080Intercepting : all TCP connections
--port: specify the port the local instance of your service is running on. If the intercepted service exposes multiple ports, specify the port you want to intercept after a colon.
--env-file: specify a file path for Telepresence to write the environment variables that are set in the pod. The example below shows Telepresence intercepting traffic going to service
example-service. Requests now reach the service on port
httpin the cluster get routed to
8080on the workstation and write the environment variables of the service to
- Start your local environment using the environment variables retrieved in the previous step.
The following are some examples of how to pass the environment variables to your local process:
- Docker: enter
docker runand provide the path to the file using the
--env-fileargument. For more information about Docker run commands, see the Docker command-line reference documentation.
- Visual Studio Code: specify the path to the environment variables file in the
envFilefield of your configuration.
- JetBrains IDE (IntelliJ, WebStorm, PyCharm, GoLand, etc.): use the EnvFile plugin.
- Query the environment in which you intercepted a service and verify your local instance being invoked. All the traffic previously routed to your Kubernetes Service is now routed to your local environment
Now, with Telepresence, you can:
- Make changes on the fly and see them reflected when interacting with your remote Kubernetes environment, this is just like hot reloading, but it works across both local and remote environments.
- Query services and microservice APIs that are only accessible in your remote cluster's network.
- Set breakpoints in your IDE and re-route remote traffic to your local machine to investigate bugs with realistic user traffic and API calls.