ClientIP+SrcPort based session persistence in IPVS
Is it possible to have a clientIP+clientPort based persistence as opposed to Just clientIP where all requests from a particular IP (but different port) goes to same node ?. IPVS (or atleast keepalived) supports this granularity in persistence. Kube-router doesn't seem to support this. To check this, i issued curl commands from a host with different --local-port option when affinity is ClientIP
@PadmabushanReddy at this point clientIP+clientPort based persistence is not there. I will check and revert back if its possible to implement it.
similar issues in kubernetes: https://github.com/kubernetes/kubernetes/issues/60688
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stale for 5 days with no activity.