Open AbelHu opened 1 year ago
@AbelHu What is the ETA for this , any follow up item to know here ?
@debj1t @daschott do you know which component/version will contain the fix?
@Debjitdj @daschott do you know which component/version will contain the fix?
@AbelHu, The fix is in Windows VFP. The fix is already in, will check with the Servicing team, and update you on the version where the fix will be available.
PS: An incorrect username is tagged in your comment.
@debj1t do you have any updae?
Describe the bug Load balancer service access with sessionAffitinity ClientIP is broken in Windows Server 2022 Windows pod can't connect to internal ingress service. Bypassing the service load balancer and connecting to the ingress pod directly works.
To Reproduce Steps to reproduce the behavior: Setting .spec.sessionAffinity to ClientIP for a Service with WS2022 https://kubernetes.io/docs/reference/networking/virtual-ips/#session-affinity
Expected behavior Connect to load balancer service successfully.
Mitigation Create services without SessionAffinity. Impact: Load distribution will happen based on the 5 tuples (Source IP, Source Port, Destination IP, Destination Port, Protocol) instead of just the Source and Destination IP.