From f536fc7abf4516ab04889faa01d6cf0a098fd4d1 Mon Sep 17 00:00:00 2001 From: Ivan Porta Date: Wed, 8 Jul 2026 13:00:33 +0200 Subject: [PATCH] update trafficDistribution docs Signed-off-by: Ivan Porta --- .../content/2-edge/features/topology-aware-routing.md | 6 +----- linkerd.io/content/2.12/features/topology-aware-routing.md | 2 +- linkerd.io/content/2.13/features/topology-aware-routing.md | 2 +- linkerd.io/content/2.14/features/topology-aware-routing.md | 2 +- linkerd.io/content/2.15/features/topology-aware-routing.md | 2 +- linkerd.io/content/2.16/features/topology-aware-routing.md | 2 +- linkerd.io/content/2.17/features/topology-aware-routing.md | 6 +----- linkerd.io/content/2.18/features/topology-aware-routing.md | 6 +----- linkerd.io/content/2.19/features/topology-aware-routing.md | 6 +----- linkerd.io/content/docs/features/topology-aware-routing.md | 6 +----- 10 files changed, 10 insertions(+), 30 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..2342588960 100644 --- a/linkerd.io/content/2-edge/features/topology-aware-routing.md +++ b/linkerd.io/content/2-edge/features/topology-aware-routing.md @@ -18,11 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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.) +endpoints whose `hints.forZones` field matches the client's zone. {{< note >}} diff --git a/linkerd.io/content/2.12/features/topology-aware-routing.md b/linkerd.io/content/2.12/features/topology-aware-routing.md index 8b20b0fdf8..e70a129c16 100644 --- a/linkerd.io/content/2.12/features/topology-aware-routing.md +++ b/linkerd.io/content/2.12/features/topology-aware-routing.md @@ -18,7 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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. +endpoints whose `hints.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 diff --git a/linkerd.io/content/2.13/features/topology-aware-routing.md b/linkerd.io/content/2.13/features/topology-aware-routing.md index 8b20b0fdf8..e70a129c16 100644 --- a/linkerd.io/content/2.13/features/topology-aware-routing.md +++ b/linkerd.io/content/2.13/features/topology-aware-routing.md @@ -18,7 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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. +endpoints whose `hints.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 diff --git a/linkerd.io/content/2.14/features/topology-aware-routing.md b/linkerd.io/content/2.14/features/topology-aware-routing.md index a92dfe12d1..077d82dd17 100644 --- a/linkerd.io/content/2.14/features/topology-aware-routing.md +++ b/linkerd.io/content/2.14/features/topology-aware-routing.md @@ -18,7 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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. +endpoints whose `hints.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 diff --git a/linkerd.io/content/2.15/features/topology-aware-routing.md b/linkerd.io/content/2.15/features/topology-aware-routing.md index a92dfe12d1..077d82dd17 100644 --- a/linkerd.io/content/2.15/features/topology-aware-routing.md +++ b/linkerd.io/content/2.15/features/topology-aware-routing.md @@ -18,7 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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. +endpoints whose `hints.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 diff --git a/linkerd.io/content/2.16/features/topology-aware-routing.md b/linkerd.io/content/2.16/features/topology-aware-routing.md index a92dfe12d1..077d82dd17 100644 --- a/linkerd.io/content/2.16/features/topology-aware-routing.md +++ b/linkerd.io/content/2.16/features/topology-aware-routing.md @@ -18,7 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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. +endpoints whose `hints.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 diff --git a/linkerd.io/content/2.17/features/topology-aware-routing.md b/linkerd.io/content/2.17/features/topology-aware-routing.md index a92dfe12d1..2342588960 100644 --- a/linkerd.io/content/2.17/features/topology-aware-routing.md +++ b/linkerd.io/content/2.17/features/topology-aware-routing.md @@ -18,11 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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.) +endpoints whose `hints.forZones` field matches the client's zone. {{< note >}} 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..2342588960 100644 --- a/linkerd.io/content/2.18/features/topology-aware-routing.md +++ b/linkerd.io/content/2.18/features/topology-aware-routing.md @@ -18,11 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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.) +endpoints whose `hints.forZones` field matches the client's zone. {{< note >}} diff --git a/linkerd.io/content/2.19/features/topology-aware-routing.md b/linkerd.io/content/2.19/features/topology-aware-routing.md index a92dfe12d1..2342588960 100644 --- a/linkerd.io/content/2.19/features/topology-aware-routing.md +++ b/linkerd.io/content/2.19/features/topology-aware-routing.md @@ -18,11 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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.) +endpoints whose `hints.forZones` field matches the client's zone. {{< note >}} diff --git a/linkerd.io/content/docs/features/topology-aware-routing.md b/linkerd.io/content/docs/features/topology-aware-routing.md index a92dfe12d1..2342588960 100644 --- a/linkerd.io/content/docs/features/topology-aware-routing.md +++ b/linkerd.io/content/docs/features/topology-aware-routing.md @@ -18,11 +18,7 @@ prefer endpoints by basing decisions solely off the node's `topology.kubernetes.io/zone` label. If a client is in `zone-a`, then it should 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.) +endpoints whose `hints.forZones` field matches the client's zone. {{< note >}}