← Directory

Telepresence-oss

Helm chart that deploys the Telepresence server-side components into a Kubernetes cluster, enabling developers to debug local services against real cluster…

  • Development
  • Infrastructure
  • Tools & Utilities
Helm chart that deploys the Telepresence server-side components into a Kubernetes cluster, enabling developers to debug local services against real cluster traffic without the container build-and-deploy cycle.

Platform availability

Available on 3 of 9 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac
  • Windows
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

80/100 Excellent

Maintained
100last commit 2 days ago
Popular
777,321 GitHub stars
Easy to install
453 install platforms, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the client on your computer Install the Telepresence client with Homebrew on macOS or the provided RPM package on Fedora/RHEL. Without it, you won’t have the Telepresence commands needed to set up or connect the cluster. source
  • Set up the cluster with setup --apply Run telepresence setup --apply to install the traffic-manager controller that routes cluster traffic to your local containers. Without it, cluster services may not be able to reach those local containers, but the command is safe to run again. source
  • Connect your computer to the cluster Run telepresence connect --namespace default after setup, because it creates the network path that lets your machine reach cluster services. If you skip it, cluster services will not be reachable, and standalone installs may ask for your password to start the root daemon. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to install a local Telepresence client to set up or connect the cluster?

Yes. Install the Telepresence client with Homebrew on macOS or the provided RPM package on Fedora/RHEL. Without it, you will not have the Telepresence commands needed to set up or connect to the cluster.

Is it safe to rerun the Telepresence cluster setup command?

Yes. telepresence setup --apply installs the traffic-manager controller that routes cluster traffic to your local containers. The documentation says the command is safe to run again.

Why are cluster services unreachable from my machine after setup?

You may need to run telepresence connect --namespace default to create the network path that lets your machine reach cluster services. If you skip it, cluster services will not be reachable.

What common Telepresence issues should I check when debugging local development?

The troubleshooting guide covers cluster connections, DNS, volume mounts, and traffic-agent injection.

Where can self-hosters get community support for Telepresence issues?

Use the community GitHub Discussions and the CNCF Slack channel for telepresence-oss. The project also points to troubleshooting documentation for common issues.

Answers sourced from github.com, github.com, github.com, github.com, telepresence.io

Community

No community discussions collected yet.