New user session spawn after update in hub configuration

Hi,
I have a kubernetes setup running and a user currently having a session (user pod).
If I make a change to the hub configuration, the hub pod is restarted and the next time the user logins, I see the below logs

I 2025-06-09 09:35:20.610 JupyterHub log:192] 302 GET /hub/spawn/radhika%20punchepady%20raju -> /hub/spawn-pending/radhika%20punchepady%20raju (radhika punchepady raju@10.57. │
│ [I 2025-06-09 09:35:20.610 JupyterHub spawner:2931] Attempting to create pvc claim-radhika-punchepady-raju---a5d8ff70, with timeout 3                                           │
│ [I 2025-06-09 09:35:20.706 JupyterHub pages:397] radhika punchepady raju is pending spawn                                                                                       │
│ [I 2025-06-09 09:35:20.708 JupyterHub log:192] 200 GET /hub/spawn-pending/radhika%20punchepady%20raju (radhika punchepady raju@10.57.0.109) 8.96ms                              │
│ [I 2025-06-09 09:35:21.384 JupyterHub spawner:2947] PVC claim-radhika-punchepady-raju---a5d8ff70 already exists, so did not create new pvc.                                     │
│ [I 2025-06-09 09:35:21.387 JupyterHub spawner:2890] Attempting to create pod jupyter-radhika-punchepady-raju---a5d8ff70, with timeout 3                                         │
│ [I 2025-06-09 09:35:22.828 JupyterHub spawner:2910] Found existing pod jupyter-radhika-punchepady-raju---a5d8ff70, attempting to kill                                           │
│ [I 2025-06-09 09:35:22.828 JupyterHub spawner:3282] Deleting pod team-presales-eu/jupyter-radhika-punchepady-raju---a5d8ff70                                                    │
│ [I 2025-06-09 09:36:49.270 JupyterHub log:192] 200 GET /hub/api/ (jupyterhub-idle-culler@::1) 16.93ms                                                                           │
│ [I 2025-06-09 09:36:49.291 JupyterHub log:192] 200 GET /hub/api/users?state=[secret] (jupyterhub-idle-culler@::1) 19.04ms

Is this expected behavior? So every time there is an application update, it will kill all the end user session (singleuser-server) and restart them?

Thanks in advance,
Radhika

By default JupyterHub shouldn’t shutdown running user servers

Can you turn on debug logging and share your logs from the hub and singleuser pods?

2 Likes