From d40a942d193f5f51e30cec75e54241a4c22035ca Mon Sep 17 00:00:00 2001 From: Ivan Porta Date: Fri, 27 Feb 2026 22:36:46 +0900 Subject: [PATCH] Remove note in TAR docs Signed-off-by: Ivan Porta --- linkerd.io/content/2-edge/features/topology-aware-routing.md | 4 ---- linkerd.io/content/2.18/features/topology-aware-routing.md | 4 ---- 2 files changed, 8 deletions(-) diff --git a/linkerd.io/content/2-edge/features/topology-aware-routing.md b/linkerd.io/content/2-edge/features/topology-aware-routing.md index a92dfe12d1..37e0307fa6 100644 --- a/linkerd.io/content/2-edge/features/topology-aware-routing.md +++ b/linkerd.io/content/2-edge/features/topology-aware-routing.md @@ -20,10 +20,6 @@ prefer endpoints marked for use by clients in `zone-a`. When the feature is enabled and the label set, Linkerd's destination controller will attempt to find endpoints whose `routing.ForZones` field matches the client's zone. -(Topology aware routing is distinct from the `trafficDistribution` feature that -appears in Kubernetes 1.31. `trafficDistribution` is not yet supported by -Linkerd.) - {{< note >}} If you're using a stable distribution of Linkerd, it may have additional diff --git a/linkerd.io/content/2.18/features/topology-aware-routing.md b/linkerd.io/content/2.18/features/topology-aware-routing.md index a92dfe12d1..37e0307fa6 100644 --- a/linkerd.io/content/2.18/features/topology-aware-routing.md +++ b/linkerd.io/content/2.18/features/topology-aware-routing.md @@ -20,10 +20,6 @@ prefer endpoints marked for use by clients in `zone-a`. When the feature is enabled and the label set, Linkerd's destination controller will attempt to find endpoints whose `routing.ForZones` field matches the client's zone. -(Topology aware routing is distinct from the `trafficDistribution` feature that -appears in Kubernetes 1.31. `trafficDistribution` is not yet supported by -Linkerd.) - {{< note >}} If you're using a stable distribution of Linkerd, it may have additional