You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I override user's resource allocation via c.KubeSpawner.options_form with a default profile (by default, I have cpu 0.5/2, memory 2gi/8gi)
In z2jh 1.2 and jupyterhub 2, I can spawn user in admin page, with default profile.
In z2jh 2.0 and jupyterhub 3, looks like if I spawm user in admin page, jupyterhub would not load my profile override, with limit resource unspecified and got error from k8s API server
Also, it works if I open spawn page and select profile
How to reproduce
In z2jh 2 and jhub 3
Specify CPU/memory via set profile _list in c.KubeSpawner.options_form
Open admin page and select user there
Expected behaviour
Actual behaviour
Your personal set up
OS:
Ubuntu 22.04, k8s 1.28.3
Full environment
# paste output of `pip freeze` or `conda list` here
Configuration
# jupyterhub_config.py
Logs
The text was updated successfully, but these errors were encountered:
Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other.
Thanks you for being an active member of our community! ❤️
Bug description
I override user's resource allocation via c.KubeSpawner.options_form with a default profile (by default, I have cpu 0.5/2, memory 2gi/8gi)
In z2jh 1.2 and jupyterhub 2, I can spawn user in admin page, with default profile.
In z2jh 2.0 and jupyterhub 3, looks like if I spawm user in admin page, jupyterhub would not load my profile override, with limit resource unspecified and got error from k8s API server
Also, it works if I open spawn page and select profile
How to reproduce
Expected behaviour
Actual behaviour
Your personal set up
Ubuntu 22.04, k8s 1.28.3
Full environment
Configuration
# jupyterhub_config.py
Logs
The text was updated successfully, but these errors were encountered: