Skip to content
Projects

telepresenceio/telepresence has 7,333 GitHub stars and 585 forks. GitHot measured +2 stars in 24 hours and +7 in 7 days. Last checked 2026-11-12 14:09 UTC. Last push 2026-11-06.

How these counts are measured

Local development against a remote Kubernetes or OpenShift cluster

What you can do

  • Cluster access - Your workstation reaches cluster Services and Pods as if it were inside the cluster: cluster DNS, cluster IPs, no port-forwards.
  • Four attachment modes - Replace the remote container, intercept a service port, wiretap a copy of the traffic, or ingest just the environment and volumes.
  • Traffic filtering - Intercept only your own requests, selected by HTTP header or path, so a whole team can share one cluster without collisions.
  • Sidecar or node-agent - The traffic-agent is either injected as a sidecar (the default), or runs as a node-hosted pod that attaches to workloads without modifying them: no injection, no pod restarts.

Measured star growth

in 24h
+2
in 7 days
+7
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

README.md

Original

Telepresence: Fast, Local Development for Kubernetes

Artifact Hub Gurubase

Telepresence is a CNCF project that connects your workstation to a Kubernetes cluster. Code and debug a service locally — with your own IDE, debugger, and hot reload — while it receives real traffic from the cluster, without the container build/push/deploy cycle.

Demo: connect, reach a cluster service, intercept it locally

Key Features

  • Cluster access - Your workstation reaches cluster Services and Pods as if it were inside the cluster: cluster DNS, cluster IPs, no port-forwards.
  • Four attachment modes - Replace the remote container, intercept a service port, wiretap a copy of the traffic, or ingest just the environment and volumes.
  • Traffic filtering - Intercept only your own requests, selected by HTTP header or path, so a whole team can share one cluster without collisions.
  • Sidecar or node-agent - The traffic-agent is either injected as a sidecar (the default), or runs as a node-hosted pod that attaches to workloads without modifying them: no injection, no pod restarts.
  • Remote environment, local process - Run with the remote container's environment variables and volume mounts, so the code behaves like it does in the cluster.

Getting Started

How It Works

When Telepresence connects, it creates a virtual network interface on your workstation and routes cluster traffic through a traffic-manager deployed in the cluster. Attaching to a workload adds a traffic-agent — a sidecar or a node-agent — that hands the workload's traffic, environment, and volumes over to your machine. See the architecture overview for the full picture.

Community

Sponsors

Telepresence is free and open source, and is kept that way by its sponsors. Sponsorship pays for fast issue responses, prompt security fixes, and new features. If your team relies on Telepresence, please consider sponsoring the project, or get in touch about a corporate sponsorship.

Thank you to our past sponsors:

Contributing

See AGENTS.md for build instructions, architecture overview, and development guidelines.

Code signing policy

The Windows binaries and installers are Authenticode-signed and distributed by Tada AB, a Swedish company founded by the lead maintainer of the Telepresence open source project, using Azure Artifact Signing.

License

Telepresence is licensed under the Apache License 2.0.

Explore related projects