Add consistent hash policy support to TrafficPolicy
Add spec.consistentHash to TrafficPolicy and merge it into route hash_policy generation.
Latest localFailed checks
Run history
Flash-Next IQ3_SDeepSWE · October 27 overnight
- Agent time
- 32m 37s
- Feature checks
- 0 / 2
- Regression checks
- 214 / 214
Run settings & provenance
- Run ID
- tonight-20261027/kgateway-consistent-hash-policy__9xkjaoa
- Model
- qwen3.8-flash-next-iq3_s
- Reasoning effort
- medium
- Requested output allowance
- 196,608
- Temperature
- 1.0
- Top p
- 0.95
- Top k
- 20
- Min p
- 0.0
- Presence penalty
- 0.0
- Repetition penalty
- 1.0
- Context
- 196,608
- Engine
- Strata 0.1.48.1 HC_Q8
- Output policy
- native remaining context
- Agent seconds limit
- 2,700
Timing, delivery & token accounting
- Timing seconds · Environment setup (seconds)
- 44.610372
- Timing seconds · Agent setup
- 0.294499
- Timing seconds · Agent execution (seconds)
- 1957.460358
- Timing seconds · Verifier
- 189.951678
- Usage · Input tokens
- 12,467,393
- Usage · Cached tokens
- 12,387,437
- Usage · Output tokens
- 61,236
- Usage · Peak context tokens
- 138,222
- Usage · Steps
- 132
- Usage · Requests
- 133
- Patch · Bytes
- 90,069
- Patch · SHA256
- 7758ab1246626147c30abe03d605c78e2d78fb9e0fc9a11f72eeae235d3cae68
- Verification · Status
- official-scored
- Verification · Verifier
- DeepSWE v1.1 official verifier
- Verification · Evidence
- verified campaign state and official verifier result
Published comparisons
No matching published results verified.
Official assignment
Recorded assignment context
Add spec.consistentHash to TrafficPolicy and merge it into route hash_policy generation.
Read the complete brief
- Add
spec.consistentHashto TrafficPolicy with these sub-fields: disable- bool that suppresses consistent hashing on a route; when true, no other fields may be setheaders- array of objects, each withheaderName, optionalregexRewrite(withpatternandsubstitution), andterminalcookies- array of objects, each withname,ttl(duration string),path,attributes(array of name/value pairs for SameSite, Secure, etc.), andterminalqueryParameters- array of objects, each withnameandterminalfilterState- array of objects, each withkeyandterminalsourceIp- object withterminal
Required Runtime Behavior
- When
consistentHashis set (even as empty{}), theRouteActionmust includehash_policyentries. If no sub-fields are specified, default to a single sourceIp hash policy with terminal=false. - When
disableis true, no hash policies are produced and any inherited from broader-scoped policies are suppressed. - Hash policy entries are built in canonical type order: headers, cookies, queryParameters, filterState, sourceIp.
- Within each array field, entries must be deduplicated by their identifying key (
headerNamefor headers,namefor cookies and queryParameters,keyfor filterState). If duplicates exist, only the first occurrence is kept. Header deduplication is case-insensitive (HTTP headers are case-insensitive), preserving the casing of the first occurrence. - When a header has
regexRewriteset, the header value is rewritten using the regex before hashing. - Cookie
ttlaccepts Go duration format (e.g. "1h30m") or plain integer seconds (e.g. "3600"). Cookieattributesare passed through to Envoy as-is. - When multiple TrafficPolicies target the same route, array fields must be unioned across both policies with the higher-priority policy's entries first, deduplicated by key. The merged result must be re-sorted into canonical type order. The
sourceIpscalar retains the higher-priority policy's value even when unset. - Merge metadata must record this field as
consistentHashunder the existing TrafficPolicy merge metadata key.
IMPORTANT: Please work on this in a new branch from main and commit everything when you are done.