Session affinity for the Controller service #86
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
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.
The text was updated successfully, but these errors were encountered: