A developer may need to change one service quickly while still using the dependencies already running in a cluster. Telepresence connects the local development environment with Kubernetes and offers modes that can redirect requests, copy traffic or expose selected workload context. This lets a local process participate in a more complete application environment. The modes have different consequences, including access to environment variables and mounted data, so choose a limited development scope and verify cleanup after detaching.
Current guidance
Current documentation distinguishes replace, intercept, wiretap and ingest attachment modes, served through traffic-agent and traffic-manager components. These modes have different effects: rerouting requests, copying traffic or only exposing configuration and volumes should not be treated as interchangeable development conveniences.
An attachment can make workload environment variables and mounted data available on a developer workstation; some modes provide writable volume access. Decide which namespaces and workloads are eligible and use credentials and datasets appropriate for development. Network reachability through the cluster is not authorization to access every production database that happens to be reachable.
For adoption or migration from older Telepresence versions, align the client and cluster components and review changed commands and interception behavior. Test routing, DNS, VPN interaction and cleanup with a disposable service. Verify that detaching restores the intended workload and that background consumers cannot run twice unintentionally. Keep ordinary image-build and deployment tests as well: local execution against remote dependencies does not prove the eventual production container contains all required files or behaves identically.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub does not mark telepresenceio/telepresence archived or disabled; this does not establish active maintenance, support or compatibility. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Telepresence is a fast and realistic local development for Kubernetes microservices.
Have you ever wanted the quick development cycle of local code while still having your code run within a remote Kubernetes cluster? Telepresence allows you to run your code locally while still:
- Giving your code access to Services in a remote Kubernetes cluster
- Giving your code access to cloud resources like AWS RDS or Google PubSub
- Allowing Kubernetes to access your code as if it were in a normal pod within the cluster
Demo
Sources & further reading
Spotted something that needs another look?
Help improve this page →