Cannot select user environment

JupyterHub Zero to JupyterHub on Kubernetes
1

I setup three profiles for user to select their environment: k8s-singleuser-sample, datascience-notebook and r-notebook. When user logins at first time, he can select one environment from the Server Options page. But when the user logouts and logins again, he always go in the selected environment automatically.

Is it possible to allow user to select environment each time when he logins?

Here is my config.yaml:

singleuser:
  # Defines the default image
  image:
    name: quay.io/jupyterhub/k8s-singleuser-sample
    tag: "3.3.8"
  profileList:
    - display_name: "K8s singleuser sample environment"
      description: "Default environment."
      default: true
    - display_name: "Datascience environment"
      description: "Python, R, and Julia."
      kubespawner_override:
        image: jupyter/datascience-notebook:ubuntu-22.04
    - display_name: "RStudio environment"
      description: "The Jupyter R image!"
      kubespawner_override:
        image: jupyter/r-notebook:ubuntu-22.04
2

The default behaviour is to direct a user to the spawn page if their singleuser server isn’t running, or to their server if it is.

You can override this:

hub:
  config:
    JupyterHub:
      default_url: "/hub/home"
3

Thanks Manics. The idea plan is each time when the user logouts and relogins, he always has chance to select different environment.
The default setting is when user logout for one hour and relogin, he has chance to select environment. I can decrease timeout to reduce the logout waiting time. But it is not idea solution. For example, in the following config, the user will select environment only after logout and wait for 60 seconds.

	cull:
	    timeout: 60
	    every: 30
4

You can set c.JupyterHub.shutdown_on_logout to shutdown all a user’s servers when they logout.

hub:
  config:
    JupyterHub:
      shutdown_on_logout: true

This isn’t perfect though. For example, if a user’s session times-out but they don’t logout their server will continue running unless it’s stopped by the idle-culler.