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

Session affinity for the Controller service #86

Open
adrianmo opened this issue Nov 15, 2018 · 2 comments
Open

Session affinity for the Controller service #86

adrianmo opened this issue Nov 15, 2018 · 2 comments
Labels
kind/enhancement Enhancement of an existing feature priority/P2 Slight inconvenience or annoyance to applications, system continues to function status/needs-investigation Further investigation is required

Comments

@adrianmo
Copy link
Contributor

adrianmo commented Nov 15, 2018

By default, Kubernetes services load balance incoming requests to all backend pods in a round robin fashion. However, there's an option to enable session affinity to services to forward traffic from a particular source IP to the same backend pod. This option is ideal to achieve better performance in the client-controller communication, where a particular client would always contact to the same controller instance and avoid extra communication between controller instances.

@adrianmo adrianmo added the kind/enhancement Enhancement of an existing feature label Nov 15, 2018
@adrianmo
Copy link
Contributor Author

@adrianmo adrianmo added priority/P1 Recoverable error, functionality/performance impaired but not lost, no permanent damage status/ready The issue is ready to be worked on; or the PR is ready to review labels Nov 21, 2018
@adrianmo
Copy link
Contributor Author

Let's be careful about source IP affinity because external clients might get their original IP translated and that might invalidate this approach. Need to explore the application-level cookie affinity approach.

@adrianmo adrianmo added priority/P2 Slight inconvenience or annoyance to applications, system continues to function status/needs-investigation Further investigation is required and removed priority/P1 Recoverable error, functionality/performance impaired but not lost, no permanent damage status/ready The issue is ready to be worked on; or the PR is ready to review labels May 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement of an existing feature priority/P2 Slight inconvenience or annoyance to applications, system continues to function status/needs-investigation Further investigation is required
Projects
None yet
Development

No branches or pull requests

1 participant