Skip to content

Remove session affinity#1097

Draft
matthew-robinson-ons wants to merge 4 commits intomainfrom
remove-session-affinity
Draft

Remove session affinity#1097
matthew-robinson-ons wants to merge 4 commits intomainfrom
remove-session-affinity

Conversation

@matthew-robinson-ons
Copy link
Copy Markdown
Contributor

@matthew-robinson-ons matthew-robinson-ons commented Mar 4, 2026

What and why?

Currently we have session affinity set to clientIP in a number of our apps including frontstage.
During performance testing it was discovered that one pod was serving all of the test script requests. Presumably because the requests are coming from a single sourceIP. It's not clear why session affinity was introduced and so the consequences of updating this need to be fully understood.

Options for session affinity:

  • None (NONE)
  • Client IP (CLIENT_IP)
  • Generated cookie (GENERATED_COOKIE)
  • Header field (HEADER_FIELD)
  • HTTP cookie (HTTP_COOKIE)
  • Stateful cookie-based affinity (STRONG_COOKIE_AFFINITY)

Setting session affinity to none is not the same as removing the session affinity. None uses a 5-tuple hash (source IP address, the source port, the protocol, the destination IP address, destination port ). As the source ip is still included in this hash, we may need to remove the session affinity completely to prevent requests being served from a single pod when coming from a single source IP.

How to test?

Jira

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants