zoom_in Click to enlarge

Telepresence

▲ ▼

language

description Telepresence Overview

Telepresence provides developers with secure, local access to Kubernetes clusters for debugging and development. It functions by running a proxy container inside the target cluster, allowing direct interaction and troubleshooting without requiring public network exposure. This tool is particularly valuable for teams working with remote or private Kubernetes deployments needing efficient developer workflows and comprehensive diagnostics.

help Telepresence FAQ

How does Telepresence route my local traffic to a Kubernetes cluster?

Telepresence works by deploying a two-way network proxy within a pod inside your Kubernetes cluster. This intercepts traffic and routes it to your local machine, allowing your local code to communicate with remote cluster services as if it were running inside the cluster itself.

Can I use Telepresence for debugging microservices without exposing them to the public internet?

Yes, Telepresence establishes a secure, encrypted VPN tunnel directly to the cluster's internal network. This allows developers to debug services locally without having to expose vulnerable pods via external load balancers or ingresses.

Is Telepresence open-source?

Telepresence was originally created by Datawire and the core technology is open-source under the Apache License. There is also a commercial version called Telepresence Enterprise, maintained by Ambassador Labs, which offers advanced features for larger teams.

Do I need cluster administrator privileges to use Telepresence?

Standard Telepresence requires certain Kubernetes RBAC permissions to install its traffic-intercepting agents. While standard developers can often use it with namespace-level permissions, cluster administrators typically need to pre-install the Traffic Manager component for enterprise deployments.

swap_horiz

Looking for Telepresence alternatives? Compare top competitors ranked & scored

arrow_forward