- Quick Start
- Custom Filters
- Deploying to Kubernetes from GitHub
- Knative Serverless Framework
- Prometheus monitoring
- The Mapping Resource
- Automatic Retries
- Canary Releases
- Circuit Breakers
- Cross-Origin Resource Sharing
- Method-Based Routing
- Prefix Regex
- Query Parameter-Based Routing
- Traffic Shadowing
- The Ambassador Module
- Custom Error Responses
- Gzip Compression
- Host CRD, ACME Support, and External Load Balancer Configuration
- Ingress Controller
- Scaling Ambassador
- Developer Portal
Telepresence can import environment variables from the cluster pod when running an intercept. You can then use these variables with the code running on your laptop of the service being intercepted.
There are three options available to do this:
telepresence intercept <service> --port <port> --env-file=<filename>
This will write the environment variables to a Docker Compose
.envfile. This file can be used with
docker-composewhen starting containers locally. Please see the Docker documentation regarding the file syntax and usage for more information.
telepresence intercept <service> --port <port> --env-json=<filename>
This will write the environment variables to a JSON file. This file can be injected into other build processes.
telepresence intercept <service> --port <port> -- <command>
This will run a command locally with the Pod's environment variables set on your laptop. Once the command quits the intercept is stopped (as if
telepresence leave <service>was run). This can be used in conjunction with a local server command, such as
node <filename>to run a service locally while using the environment variables that were set on the pod via a ConfigMap or other means.
Another use would be running a subshell, Bash for example:
telepresence intercept <service> --port <port> -- /bin/bash
This would start the intercept then launch the subshell on your laptop with all the same variables set as on the pod.