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