Feature Request - Support a Wider Range of Hash Policies
See original GitHub issueCurrently, with the v1 Envoy API, hash_policy
annotations are limited to header
. The v2 API offers additional hash policies including cookie
and source_ip
. Additionally, both with the v1 and v2 APIs an envoy_override
is required to actually implement this. Native support in annotations would be ideal.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
A Guide to Consistent Hashing - Toptal
First, a good hash function generally has a wide output range (typically, the whole range of a 32 or 64-bit integer), so building...
Read more >Consistent hashing explained | Ably Blog: Data in Motion
Theoretically, each server node 'owns' a range of the hashring, and any requests coming in at this range will be served by the...
Read more >INTRODUCTION TO THE HASH FUNCTION AS A ...
This essay is intended for data controllers who wish to use hash techniques ... This increasing demand for personal data has entailed a...
Read more >When to Use Hash Partitioning
With hash partitioning, a row is placed into a partition based on the result of passing the partitioning key into a hashing algorithm....
Read more >Features and terminology in Azure Event Hubs - Microsoft Learn
This article provides details about features and terminology of Azure Event Hubs.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kflynn Are there any up-to-date docs on what, if any,
envoy_override
s are supported currently?@kflynn any updates regarding this? You say that
envoy_override.hash_policy
should be supported by 0.50 in #951 , but there are no docs for session affinity at getambassador.io 😞 Looking at envoy v2 configs, they support affinity well but I have no idea how I would use that in ambassador.