[Bug]: Kubernetes session affinity not working with remote Jupyter code executor deployment

[timrbula]

Describe the bug

I am intermittently seeing 404 Kernel does not exist errors when running remote Jupyter execution in an OpenShift cluster that has multiple pods each running Jupyter Kernel Gateway and cookie-based session affinity is enabled.

• nginx session affinity
• OpenShift Route Statefulness

Steps to reproduce

1. Create a deployment of the Jupyter Kernel Gateway container as described in the custom docker image docs running multiple pods.
2. Create an associated service and ingress and add the appropriate cookie annotation for session affinity.
3. Run multiple AutoGen workflows concurrently that use the remote Jupyter Code Executor.

Model Used

N/A

Expected Behavior

The kernel should be found when trying to establish the web socket connection by communicating with the same pod that the kernel was created in.

Screenshots and logs

No response

Additional Information

No response