Closed lucianolacurcia closed 1 year ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
You are in control of what memory limits etc you declare on the singleuser pods, those spawned by KubeSpawner. In the JupyterHub Helm chart, it will be configured under singleuser.memory
, see https://z2jh.jupyter.org/en/stable/resources/reference.html#singleuser-memory.
If you have a ResourceQuota that enforces values to be set, or to be in a certain range etc, its a matter of configuration of KubeSpawner to work against your provided ResourceQuota I assume. Thinking that, I see no action point or something to fix in this repo and will go for a close.
Thanks, the problem was my mistake, I was already setting the singleuser.memory.limit as the ResourceQuota enforces, but I was not setting on the network tools container, so that why the error was occurring.
Thanks!
Bug description
Unable to set ResourceQuota for limiting memory on jupyterhub namespace. When pods are spawned they appear to not have the resource.limits.memory value required by the ResourceQuota. When the singleuser pods is spawned by the hub by sending the request to kubernetes api, it gets 403 error.
Expected behaviour
The pod is spawned if it fits on the quota or is not spawned if doesnt fit on the quota.
Actual behaviour
This is what the hub sends to the kubernetes api:
This is the payload of the kubernetes response:
How to reproduce
Your personal set up
Jupyterhub chart 2.0.0