.svg){kind=small}
Ingress, egress, east-west, north-south… Kubernetes has always had a lot of different ways to talk about network traffic, each with its own concerns. For years, the possibility of unifying these kinds of configuration under a single API was a tantalizing but far-off possibility until Gateway API v0.8 took the first step of combining ingress and mesh configuration. Now Linkerd is stepping up to use Gateway API to handle egress as well. Watch this hot-off-the-presses look into what egress policy covers and what people need from it, how we can make egress functionality work within Gateway API's existing model, and why Linkerd took this approach. We touch on the implementation and finish up with a live demo showing off a real-world example of egress management using Linkerd and Gateway API.
.svg)
