Skip to content

Commit 7d1822a

Browse files
committed
Update docs
Signed-off-by: jukie <10012479+jukie@users.noreply.github.com>
1 parent 3710147 commit 7d1822a

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

site/content/en/latest/tasks/traffic/zone-aware-routing.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,13 +20,13 @@ The `zoneAware` field supports two modes: `preferLocal` (prefer same-zone endpoi
2020
| `RoundRobin` |||
2121
| `LeastRequest` |||
2222
| `Random` |||
23-
| `ConsistentHash` || |
23+
| `ConsistentHash` || |
2424
| `BackendUtilization` |||
2525
| `DynamicModule` |||
2626

2727
**Why some combinations are unsupported:**
2828

29-
- **`ConsistentHash` + any zone-aware mode**: Neither `preferLocal` nor `weightedZones` are currently supported. `weightedZones` support is planned (see [#8146](https://github.com/envoyproxy/gateway/issues/8146)).
29+
- **`ConsistentHash` + `preferLocal`**: Envoy's consistent hashing policies (Maglev/RingHash) route based on a request hash rather than endpoint locality, so the prefer-local algorithm cannot be layered on top. Use `weightedZones` to influence traffic distribution across zones while preserving hash-based affinity.
3030
- **`BackendUtilization` + `preferLocal`**: Envoy's `wrr_locality` extension, which wraps `BackendUtilization` with locality-weight support, does not implement the prefer-local routing algorithm. Only `weightedZones` is supported.
3131
- **`DynamicModule` + any zone-aware mode**: Custom load balancing modules manage their own endpoint selection entirely. Zone-aware routing cannot be layered on top of an opaque third-party algorithm.
3232

@@ -194,7 +194,7 @@ spec:
194194

195195
#### WeightedZones
196196
`weightedZones` distributes traffic across zones proportionally according to explicit weights. Zones not listed receive a default weight of 1.
197-
This mode is supported by `RoundRobin`, `LeastRequest`, `Random`, and `BackendUtilization`.
197+
This mode is supported by `RoundRobin`, `LeastRequest`, `Random`, `ConsistentHash`, and `BackendUtilization`.
198198

199199
The example below routes 70% of traffic to `us-east-1a` and 30% to `us-east-1b` using `BackendUtilization`, which combines ORCA-based backend load metrics with locality weighting via Envoy's `wrr_locality` extension.
200200

0 commit comments

Comments
 (0)