Linkerd is a service mesh for cloud-native microservices that provides failure resiliency, observability, and security.
- The Gateway API standardizes some of the Ingress stuff and is mostly for North-South traffic.
- Linkerd is working on adapting the HTTP route resources to make sense for East-West traffic.
- If all pods start returning 500 errors all at once, they will all be taken out of circulation and apply the back-off penalty.
- Linkerd does not yet support IPv6, but it is in the books.
- EBPF is a cool technology, but it cannot do any State Management inside of it, making it difficult to handle circuit breaking, retries, and timeouts.
- Linkerd supports EBPF, but when it comes to doing service mesh things, there is no substitute for the sidecar proxy.
The presenter mentioned that if all pods start returning 500 errors all at once, they will all be taken out of circulation and apply the back-off penalty. If one of them comes back on, they will probe it, and if it works, they will start routing requests to it. Otherwise, tough luck.