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
There are some inconsistencies with how we reference captured in the docs vs. the codebase. We should add more context around references to things like captured and redirect or make it more consistent. For example, waypoint capture isn't an entirely accurate term and our codebase should reflect this. It's also not the term that's used in our public docs. Capture typically refers to the ztunnel traffic and not the waypoint traffic.
Getting traffic from workload into the mesh could be capture or redirect
Sending in mesh traffic through a waypoint could be redirect, reroute or detour
P.S. This is a non-urgent task and can be completed after the 1.22 beta release docs are updated first. The docs have higher priority due to their public facing nature.
The text was updated successfully, but these errors were encountered:
There are some inconsistencies with how we reference captured in the docs vs. the codebase. We should add more context around references to things like captured and redirect or make it more consistent. For example, waypoint capture isn't an entirely accurate term and our codebase should reflect this. It's also not the term that's used in our public docs. Capture typically refers to the ztunnel traffic and not the waypoint traffic.
capture
orredirect
redirect
,reroute
ordetour
slack link for context
P.S. This is a non-urgent task and can be completed after the 1.22 beta release docs are updated first. The docs have higher priority due to their public facing nature.
The text was updated successfully, but these errors were encountered: