Skip to content

update trafficDistribution docs #2145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
travisbeckham merged 1 commit into from
Jul 9, 2026
Merged

update trafficDistribution docs #2145

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions linkerd.io/content/2-edge/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 >}}

Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.12/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.13/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.14/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.15/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.16/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
6 changes: 1 addition & 5 deletions linkerd.io/content/2.17/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 >}}

Expand Down
6 changes: 1 addition & 5 deletions linkerd.io/content/2.18/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 >}}

Expand Down
6 changes: 1 addition & 5 deletions linkerd.io/content/2.19/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 >}}

Expand Down
6 changes: 1 addition & 5 deletions linkerd.io/content/docs/features/topology-aware-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 >}}

Expand Down
Loading