You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Lapdev Sidecar Proxy (automatically injected by Lapdev into each pod in managed environments):
99
+
The Lapdev Sidecar Proxy (automatically injected by Lapdev into each pod in managed environments) sits in front of your workload traffic:
100
100
101
-
1. Intercepts outgoing HTTP requests from your service
101
+
1. Intercepts incoming requests headed to your service
102
102
2. Reads the `tracestate` header to identify the branch
103
103
3. Checks if the target service has a branch override for this branch
104
-
4.Routes to the branched version if it exists
105
-
5.Routes to the shared environment if no override exists
106
-
6. The header continues to propagate to the next service
104
+
4.If a Devbox intercept is active for this branch/service, routes to the developer’s local process; otherwise routes to the branched service if present
105
+
5.Falls back to the shared environment if no branch-specific target exists
106
+
6. The header continues downstream, so the next hop can repeat the decision
107
107
108
108
> **Note:** The sidecar proxy is automatically added when Lapdev creates your environment. No manual configuration needed. For more details, see [Traffic Routing Architecture](traffic-routing-architecture.md).
0 commit comments