
A guide to modern Kubernetes network policies
In the world of Kubernetes, network policies are essential for controlling traffic within your cluster. But what are they really? And why, when and how should you implement them?
Service mesh and inference posts and tutorials from the Buoyant team.

In the world of Kubernetes, network policies are essential for controlling traffic within your cluster. But what are they really? And why, when and how should you implement them?

Today we're happy to announce Linkerd 2.16, a major step forward for Linkerd that adds a whole host of new features, including support for IPv6; an "audit mode" for Linkerd's zero trust security policies; a new implementation of retries, timeouts, and per-route metrics for HTTPRoute and GPRCRoute resources; and much more.

In this guide we'll walk you through a task that is increasingly common in the Kubernetes space: migrating an existing Istio deployment to Linkerd.

Transitioning core service mesh functionality between Istio and Linkerd is not overly complicated. Chances are you're using Istio for things that Linkerd also supports.

We're happy to announce the release of Buoyant Enterprise for Linkerd 2.15.5. This latest stable release fixes a potential panic in the destination controller, and includes a fix for CVE-2024-40632, a low criticality CVE in Linkerd.

Part I of this post covered TAR, a Kubernetes feature that restricts traffic within an availability zone from crossing to other zones, cutting cloud spend. But TAR is not without drawbacks: it can lead to worse overall system reliability.

We're happy to announce the release of Buoyant Enterprise for Linkerd 2.15.4. This latest stable release includes several backported bug fixes, especially around HTTPRoutes, as well as usability improvements and new diagnostic and configuration features.

Topology Aware Routing is a feature of Kubernetes that prevents cluster traffic within one availability zone from crossing to another availability zone. For high-traffic applications deployed in multi-zone clusters, this can provide significant cost savings. However, Topology Aware Routing is designed to always prohibit cross-zone traffic, regardless of overall system health or performance.

Today we're happy to announce the release of Buoyant Enterprise for Linkerd 2.15.3. This latest stable release includes several backported bug fixes, especially for native sidecars, as well as introducing usability improvements and new diagnostic and configuration features.

We had a blast connecting with the Linkerd community in beautiful Paris at KubeCon, and recordings of all talks are now live. The Linkerd crew was out in full force, spreading the word about how the CNCF-graduated service mesh provides critical security, reliability, and observability to Kubernetes clusters everywhere.

Today, we're happy to announce pod-based pricing for Buoyant Enterprise for Linkerd. This new pricing is designed to give our adopters a clear way and transparent picture of the cost of BEL, to be fair and commensurate with Linkerd's value, and to avoid penalizing specific architectural decisions and technical decisions that are independent of how Linkerd is used.

How can we ensure that Linkerd works on any Kubernetes cluster, regardless of Kubernetes version, distribution, architecture, and provider? While Kubernetes has become a standard for cloud applications in part because of its promise of universality, for a service mesh like Linkerd, the reality is that Kubernetes is far from uniform.