OSSTeamEnterprise
Incoming Traffic
How mirrord handles incoming network traffic from the cluster
Last updated
Was this helpful?
How mirrord handles incoming network traffic from the cluster
mirrord lets your local process receive network traffic that would normally go to a pod in the cluster. There are two modes:
In the default configuration, mirrord mirrors incoming TCP traffic - your local process receives a copy of the traffic while the remote pod continues to handle it normally. Responses from your local process are dropped. This is a safe, read-only way to observe how your code handles real requests.
In steal mode, mirrord intercepts incoming traffic and redirects it to your local process instead of the remote pod. Your local process becomes the one responding to real requests. This is useful when you need to test how your code handles and responds to live traffic.
Steal mode can be configured in your mirrord config:
{
"feature": {
"network": {
"incoming": "steal"
}
}
}Filter Incoming Traffic - Steal only a subset of traffic using HTTP header, W3C baggage/tracestate, path, or method filters
Filtering by JSON Body - Filter based on request body content
Debug from Browser - Use the Chrome extension to route browser traffic to your local process
Steal HTTPS Requests [Teams] - Decrypt and steal HTTPS traffic using TLS certificates
Inspect Live Traffic - Monitor incoming traffic without running a local process
Last updated
Was this helpful?
Was this helpful?

