Add support for session affinity during weighted routing with Istio #1280
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.
Add support for session affinity/sticky sessions during weighted routing with Istio, i.e. when a user is routed to the canary deployment, all subsequent requests from that user will hit the canary deployments, even though weighted routing is active.
This feature can be enabled by specifying a
.spec.analysis.sessionAffinty.cookieName
. This value combined with a random sequence (<cookie-name>: <random-sequence>
) is used as the value of theSet-Cookie
header, and then all requests' headers that match against this value are sent to the canary deployment. Users can also specify.spec.analysis.sessionAffinity.maxAge
to configure the lifetime of the cookie being set.Fixes: #1198, #1232