Policies · Mesh* policies
MeshLoadBalancingStrategy
Load-balancing algorithm, hash policies and locality awareness for outbound traffic.
Behaviour per target
Output: MeshLoadBalancingStrategy
to[].default.loadBalancer.{ringHash,maglev}.hashPolicies→to[].default.hashPolicies(auto-fixed).hashPolicies[].type: SourceIP→type: Connectionwithconnection.sourceIP: true(auto-fixed, at either location). 2.14 acceptsSourceIPbut builds no Envoy hash policy from it, so source-IP hashing starts to take effect once the output is applied; the warning says so.
Output: MeshLoadBalancingStrategy
v2 rewrites (3.0 removes SourceIP from the enum and rejects it), plus:
to[].default.localityAwareness.crossZoneon an entry whosetargetRef.kindis notMeshMultiZoneServiceis reported; 3.0 rejects it.- Labels-only refs and control-plane label removal. Allowed
to[].targetRef.kind:Mesh,MeshService,MeshExternalService,MeshMultiZoneService,MeshHTTPRoute.
Timeline
| Version | Change |
|---|---|
| 2.10 | hashPolicies.type: SourceIP removed. |
| 3.0 | Load-balancer-specific hashPolicies removed. crossZone requires a MeshMultiZoneService target. |
Related topics
- Multizone — Control plane modes, which control plane to extract from, zone proxies, MeshMultiZoneService and cross-zone load balancing across 2.x and 3.0.
- Policy targeting — Which targetRef kinds each policy accepts at each position on 2.14 and 3.0, labels-only selection, policy roles, and control-plane-owned labels.