This week on The Business of Open Source, I have an episode recorded on site at KubeCon EU in Paris with William Morgan, CEO of Buoyant. We had a fabulous conversation, which touched on some touchy subjects, including Buoyant’s slightly changing relationship with Linkerd.

Read about Rust, and you hear claims that seem too good to be true: memory safety, zero-cost abstractions, blazing speed…all at the same time? Back in 2018, the Linkerd project chose Rust for its data plane, betting that the language really would deliver the kind of speed and security that handling user data required.

If you’re looking into cloud native Progressive Delivery, you are likely considering Argo Rollouts or Flagger. Part of popular, graduated CNCF projects – Argo and Flux, respectively – both tie seamlessly into GitOps.

William Morgan, founder of the Linkerd service mesh and CEO of Buoyant, joins SE Radio’s Robert Blumen for a discussion of sidecars, service mesh, and a forthcoming enhancement to kubernetes to support sidecars natively.

Linkerd has long had support for allowing communication across cluster boundaries that’s secure, independent of network topology, and completely transparent to the application. This support was designed for a world in which individual clusters were generally isolated from one another, and crossing the cluster boundary was a bit unusual.

Linkerd is the first service mesh, and it is still - by far - the least stressful way to add security, reliability, and observability to any Kubernetes cluster. Using a mesh to add these critical functions at the platform layer means your application developers don’t need to worry about them! Join us to learn how it all works, and how Linkerd means we can have enterprise power without enterprise complexity!