DocsTelepresenceIntercepts
Intercepts
When intercepting a service, the Telepresence Traffic Manager ensures that a Traffic Agent has been injected into the intercepted workload. The injection is triggered by a Kubernetes Mutating Webhook and will only happen once. The Traffic Agent is responsible for redirecting intercepted traffic to the developer's workstation.
An intercept is either global or personal.
Global intercet
This intercept will intercept alltcp
and/or udp
traffic to the
intercepted service and send all of that traffic down to the developer's
workstation. This means that a global intercept will affect all users of
the intercepted service.
Personal intercept
This intercept will intercept specific HTTP requests, allowing other HTTP requests through to the regular service. The selection is based on http headers or paths, and allows for intercepts which only intercept traffic tagged as belonging to a given developer.
There are two ways of configuring an intercept:
- one from the CLI directly
- one from an Intercept Specification
Supported workloads
Kubernetes has various
workloads.
Currently, Telepresence supports intercepting (installing a
traffic-agent on) Deployments
, ReplicaSets
, and StatefulSets
.