Vinicius D. Cerutti
Vinicius D. Cerutti
Hi @leej3 thanks for opening this issue, we will be discussing this soon.
Hi @costrouc, do they want a config per user structure, or they are happy to get it set in the `qhub-config`?
This can also be achieved using overrides on the jupyterhub configuration to change the idle-culling variable values. Right now, the values that can be changed are those [here](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/bb951c581a765d185e70aed7f5f23745c81a1d8f/jupyterhub/values.yaml#L646-L654) ```yaml jupyterhub:...
There seems to be a default config yaml that can be loaded in here `https://gateway.dask.org/configuration-user.html#default-configuration` which has the luster options in it -- we might be able to set the...
c.c @costrouc I think this might help as well https://docs.dask.org/en/latest/deploying-kubernetes-helm.html?highlight=conda%20environemt#matching-the-user-environment
We can set the `filesystem/dask` env as default, which can be overwritten easily using the cluster options GUI. The only issue is that cant automatically detect the active environment with...
HI @Chris Ostrouchov about the Gateway default option for cluster env, what do you think of using the above approach?
c.c. @costrouc what are your thoughts on this?
c.c @magsol, @iameskild @Adam-D-Lewis any ideas that we may use for this?
For now, due to some uncertainty of the problem. We will add some docs on the user FAQ to address this issue and add a workaround for that.