Question about cross-site routing and session-aware behavior

32 views
Skip to first unread message

Dhia Gharsallaoui

unread,
Oct 24, 2025, 11:23:21 AM10/24/25
to Skupper
Hello,

Thank you for maintaining Skupper, I really appreciate this project.

I have a question about cross-site routing: when I create two connectors in different sites that match the same listener, is it possible to achieve session-aware routing between them?

Best regards,
Dhia Gharsallaoui

Christian Kruse

unread,
Oct 25, 2025, 11:08:05 PM10/25/25
to Skupper
Hi Dhia,

Thank you for reaching out. No, this is not presently an option. At a given listener, skupper routes traffic to the connector in the network it has the fewest open connections to (with an offset for the cumulative routing link cost.)

That said, this is an area we are actively looking to explore. I would be curious to hear specifics on what you are looking for in session-aware routing. Source IP based, HTTP header/cookie/url parameter, something else?

Cheers,
Christian

Dhia Gharsallaoui

unread,
Jan 15, 2026, 9:32:23 AMJan 15
to Skupper

Hi Christian,

Thanks for the clarification.

My use case involves inference workloads where each user has an in-memory session context. If requests from the same user get routed to different connectors/pods, that context is lost and the session breaks. So I’m looking for session-aware (sticky) routing to consistently route a given user/session to the same connector.

HTTP-level affinity would work best for us (e.g. session ID via header or cookie). Source IP–based routing would be less reliable due to NAT and proxies.

Hope this helps clarify the need.

Best regards,
Dhia

Reply all
Reply to author
Forward
0 new messages