Source: thenewstack.io
eBPF or Not, Sidecars are the Future of the Service Mesh
https://www.linkedin.com/in/wmorgan/ https://thenewstack.io/linux-technology-for-the-new-year-ebpf/ is a hot topic in the https://thenewstack.io/category/kubernetes/ world, and the idea of using it to build a “sidecar-free service mesh” has generated recent buzz. Proponents of this idea claim that eBPF lets them https://thenewstack.io/how-ebpf-streamlines-the-service-mesh/ by removing sidecars.
In fact, the service mesh market has seen this first-hand: the first service mesh, Linkerd 1.0 offered a “sidecar-free” service mesh circa 2017 using the same per-host proxy model, and the resulting challenges in operations, management, and security led directly to https://linkerd.io/2018/09/18/announcing-linkerd-2-0/ based on sidecars.
eBPF has a future in the service meshwork, but it will be as eBPF and sidecars, not eBPF or sidecars.
Like most service meshes, Linkerd does this by inserting a proxy into each application pod — the proverbial sidecar.
In fact, the service mesh market has seen this first-hand: the first service mesh, Linkerd 1.0 offered a “sidecar-free” service mesh circa 2017 using the same per-host proxy model, and the resulting challenges in operations, management, and security led directly to https://linkerd.io/2018/09/18/announcing-linkerd-2-0/ based on sidecars.
eBPF has a future in the service meshwork, but it will be as eBPF and sidecars, not eBPF or sidecars.
Like most service meshes, Linkerd does this by inserting a proxy into each application pod — the proverbial sidecar.
Related Articles
Community Partners
DevOps Careers