Ross ROSS = Recommend OSS · open-source software intelligence for agents

telepresenceio/telepresence

Local development against a remote Kubernetes or OpenShift cluster observed · 2026-08-28

github.com/telepresenceio/telepresence · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

98/100

  • Activity 99
  • Release rhythm 96
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: 10.0
  • age_days: 3478
  • days_rel: 31
  • days_push: 8
  • n_releases_24m: 45

Full methodology

Adoption not part of the score

7288 stars · 579 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Telepresence is a CNCF open-source CLI tool that connects a developer's workstation to a remote Kubernetes or OpenShift cluster, creating a virtual network interface so local code can reach cluster services and DNS as if it ran inside the cluster. It can intercept, replace, wiretap, or ingest a workload's traffic, environment variables, and volumes, letting developers debug locally with their own IDE while receiving real cluster traffic.

Use cases

  • debug a kubernetes service locally without rebuilding containers
  • run one microservice on my laptop connected to a remote cluster
  • intercept cluster traffic to my local process for testing
  • access cluster services and DNS from my workstation
  • test code changes against remote dependencies without deploying
  • share a dev cluster across a team with per-user traffic filtering
  • develop against openshift or minikube from local machine

When to choose

  • you develop microservices on Kubernetes and the build/push/deploy loop is slow
  • you want to use your local IDE, debugger, and hot reload against real cluster traffic
  • you need local code to reach cluster Services, DNS, and IPs without port-forwards
  • your team shares one dev cluster and needs per-developer traffic filtering

When to avoid

  • your app runs entirely locally or in Docker Compose with no Kubernetes dependency
  • you cannot install cluster-side components (traffic-manager requires cluster-admin once)
  • you only need simple port-forwarding without traffic interception
  • you work with non-Kubernetes platforms like serverless or VM-based deployments

Facets

cli-tool · maturity active

proxy networking developer-tools deployment http-server developer-tools cloud-computing microservices backend windows cli go kubernetes local-development traffic-intercept remote-debugging tunnel cncf openshift minikube devops containers linux macos docker

5 sources

Member repositories

RepositoryRoleHealth v2
telepresenceio/telepresencemain98

For agents

markdown · JSON · MCP: product_card(name="telepresenceio/telepresence")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem