|
- Home | Telepresence
Telepresence consists of two core architecture components: the client-side telepresence binary (CLI on your workstation) and the cluster-side traffic-manager and traffic-agent (on the remote Kubernetes cluster)
- Laptop-side configuration | Telepresence
There are a number of configuration values that can be tweaked to change how Telepresence behaves
- Client reference | Telepresence
The Telepresence CLI client is used to connect Telepresence to your cluster, start and stop intercepts, and create preview URLs All commands are run in the form of telepresence <command>
- Release Notes | Telepresence
The workload and pod annotations used by Telepresence will now use the prefix telepresence io instead of telepresence getambassador io The new prefix is consistent with the prefix used by labels, and it also matches the host name of the documentation site
- Quick start | Telepresence
Telepresence is an open source tool that enables you to set up remote development environments for Kubernetes where you can still use all of your favorite local tools like IDEs, debuggers, and profilers
- Using Telepresence with Docker | Telepresence
Using the Docker mode of telepresence does not require root access, and makes it easier to adopt it across your organization It limits the potential networking issues you can encounter
- Code and debug an application locally | Telepresence
Start using Telepresence in your own environment Follow these steps to work locally with cluster applications
- Laptop-side configuration | Telepresence
There are a number of configuration values that can be tweaked to change how Telepresence behaves
|
|
|