- 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
The Traffic Manager is the central point of communication between Traffic Agents in the cluster and Telepresence daemons on developer workstations, proxying all relevant inbound and outbound traffic and tracking active intercepts. When Telepresence is run with either the
list commands, the client first checks the cluster for the Traffic Manager deployment, and if missing it creates it.
The Traffic Agent is a sidecar container that facilitates intercepts. When an intercept is started, the Traffic Agent container is injected into the deployment's pod(s). You can see the Traffic Agent's status by running
kubectl describe pod <pod-name>.
Using Ambassador's previous offering, Service Preview, the Traffic Agent had to be manually added to a pod by an annotation. This is no longer required as the Traffic Agent is automatically injected when an intercept is started.
Service Preview also started an intercept via
edgectl intercept. The
edgectl CLI is no longer required to intercept as this functionality has been moved to the Telepresence CLI.
For both the Traffic Manager and Traffic Agents, configuring Kubernetes ClusterRoles and ClusterRoleBindings is not required as it was in Service Preview. Instead, the user running Telepresence must already have sufficient permissions in the cluster to add and modify deployments in the cluster.