You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We now propagate the session affinity fields from the exported Service to the aggregated ServiceImport. Currently this is to support MCS compliance and other integrations, eg Istio, that may utilize it. We should also consider implementing it in the CoreDNS plugin wrt service ClusterIPs, ie keep a client, identified by its IP, routed to the same cluster IP after the first request instead of always round-robin. We'd also need to determine what the behavior should be if the constituent exported services conflict wrt the SessionAffinity field.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.
We now propagate the session affinity fields from the exported
Service
to the aggregatedServiceImport
. Currently this is to support MCS compliance and other integrations, egIstio
, that may utilize it. We should also consider implementing it in the CoreDNS plugin wrt service ClusterIPs, ie keep a client, identified by its IP, routed to the same cluster IP after the first request instead of always round-robin. We'd also need to determine what the behavior should be if the constituent exported services conflict wrt theSessionAffinity
field.The text was updated successfully, but these errors were encountered: