Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sticky-session for path based routing with envoy as sidecar proxy #8888

Closed
vichooz opened this issue Nov 5, 2019 · 4 comments
Closed

Sticky-session for path based routing with envoy as sidecar proxy #8888

vichooz opened this issue Nov 5, 2019 · 4 comments
Labels
area/load balancing question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently

Comments

@vichooz
Copy link

vichooz commented Nov 5, 2019

My apologies if this comes as a beginner's question

I'd like to understand if the following scenario is supported by envoy-proxy

  • the first user’s request comes in without session information
  • the request bypass the session server choice since it has no session information
  • the request pass through the routing algorithm, where a server is chosen and affected to the client
  • the server answers back, setting its own session information
  • depending on its configuration, envoy router/LB can either use this session information or setup its own before sending the response back to the client
  • the client sends a second request, now with session information he learnt during the first request
  • the router/LB choose the server based on the client side information
  • the request DOES NOT PASS THROUGH the load-balancing algorithm
  • the server answers the request

If it is, are there any examples that I can take a look at for understanding the configurations better? Thanks

@snowp snowp added the question Questions that are neither investigations, bugs, nor enhancements label Nov 5, 2019
@mattklein123
Copy link
Member

TL/DR we don't support this today, but this is also discussed in #7218. There hasn't been a good proposal yet on how we would encode upstream information into the session cookie.

@stale
Copy link

stale bot commented Dec 8, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Dec 8, 2019
@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label Dec 8, 2019
@stale
Copy link

stale bot commented Jan 7, 2020

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Jan 7, 2020
@stale
Copy link

stale bot commented Jan 14, 2020

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/load balancing question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

4 participants