This repository has been archived by the owner on Apr 27, 2021. It is now read-only.
Introduce an upstream-hash-by annotation to support consistent hashing by nginx variable #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g by nginx variable
methodmissing
force-pushed
the
upstream-hash
branch
from
6bcfde3
to
19bf10e
Compare
|
cool, lets get this upstream as well when you're done. You just have to sign a contributor agreement thing. |
n1koo
reviewed
Oct 2, 2017
| @@ -106,6 +108,14 @@ In NGINX, backend server pools are called "[upstreams](http://nginx.org/en/docs/ | |||
|
|
|||
| Please check the [custom upstream check](../../examples/customization/custom-upstream-check/README.md) example. | |||
|
|
|||
| ### Custom NGINX upstream hashing | |||
n1koo
approved these changes
Oct 2, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proof of concept for services that require stickiness through means other than cookies or client IP.
@n1koo @karanthukral @ElvinEfendi @ibawt @mkobetic